I designed a repeatable method for reconciling fragmented sources without silently resolving conflicts.
Operational System
Canonical Source Synthesis System
A controlled method for converting duplicate, partial, and conflicting source material into evidence-linked recommendations, human-approved canonical references, and reusable operating packets.
The work at a glance
Inspect the source inventory and conflict matrix, then trace a recommendation through human approval.
Public examples use synthetic sources; organizational deployment still requires approved repositories, controls, and ownership.
The information problem
People can spend more time locating and reconciling sources than using the information.
Operational information often exists across duplicate files, emails, partial records, conflicting drafts, outdated templates, and multiple tools. A summary alone can hide disagreement or erase a unique detail.
The Canonical Source Synthesis System inventories what exists, groups related documents, links claims to evidence, isolates conflict, and stages recommendations for explicit approval. It reduces comparison burden without allowing an agent to declare a source canonical.
Representative source inventory
Make the information landscape visible before synthesizing it.
The synthetic example demonstrates how the system distinguishes version, authority, completeness, conflict, and unique value.
| Source | Document family | Status | Unique value | Control note |
|---|---|---|---|---|
| Workflow_Guide_v3.docx | Deliverable workflow | Most recent draft | Updated role sequence and revised metadata table | Not approved; compare against signed procedure |
| PRO-0205_Approved.pdf | Deliverable workflow | Approved authority | Formal requirements and approval date | Canonical authority for policy statements |
| Reviewer_Notes.xlsx | Implementation feedback | Working record | Known exceptions and user confusion points | Evidence for guidance changes, not policy authority |
| Training_Deck_Final.pptx | User enablement | Published training | Examples and screenshots not present elsewhere | Verify against current system behavior |
| Email_Clarification.msg | Decision record | Unincorporated clarification | Approved interpretation for one ambiguous step | Route for formal incorporation and owner confirmation |
Conflict and recommendation matrix
Preserve disagreement, then ask an accountable person to decide.
Recommendations are evidence-backed and reversible until approved.
| Topic | Evidence A | Evidence B | Prepared recommendation | Required decision |
|---|---|---|---|---|
| Who submits the package? | Approved procedure assigns the contributor | Training deck shows document control initiating submission | Retain contributor responsibility and revise the training example | Process owner confirms role assignment |
| Required metadata field | Procedure lists Project ID | Current system requires Project Number | Document both terms and map the approved identifier to current interface language | System owner and document-control lead approve wording |
| Review turnaround | Guide states five business days | Email clarification allows seven for complex packages | Keep five-day standard and add an approved exception rule | Process owner determines whether clarification becomes policy |
Control flow
Inventory, compare, recommend, approve, publish.
The system separates preparation from authority so the work can move faster without obscuring who made the decision.
Inventory
Record source, owner, date, version, format, authority, and access.
Cluster
Group document families, duplicates, superseded versions, and related decision records.
Compare
Map agreements, conflicts, gaps, unique details, and evidence quality.
Review
Present recommendations, uncertainty, impact, and required owner decisions.
Publish
Create the approved reference, output packets, archive record, and change history.
Reusable outputs
The result is an operating packet, not just a summary.
Each output is tied to approved evidence, audience, purpose, and maintenance ownership.
Document inventory
Complete list of files, owners, dates, versions, authority, access, and relationships.
Claim and recommendation matrix
Every proposed statement linked to the sources that support or challenge it.
Conflict and decision queue
Unresolved questions, competing evidence, impact, accountable owner, and disposition.
Approved source
The designated reference after accountable review, with effective date and approval history.
Operating packets
Guides, checklists, briefings, FAQs, and training materials generated from the approved source.
Change-control record
Requested updates, evidence, reviewer, decision, publication date, and superseded material.
Selected design decisions
Synthesis must remain traceable and reversible.
- Inventory sources before asking for conclusions.
- Separate authority, recency, completeness, and usefulness.
- Preserve unique details even when a source is not canonical.
- Link every recommendation to supporting and conflicting evidence.
- Stage changes in a review queue before publication.
- Keep canonical designation, policy interpretation, and final approval human-only.
Current maturity and boundaries
The system has been used as a repeatable method for complex information-management tasks and is documented as an operational workflow. Public examples use synthetic source records. A production implementation would require approved repositories, access controls, retention rules, process ownership, audit requirements, and validation against the organization's governing sources.