Supporting service · Intelligence
System-of-Record Architecture
One authoritative source of truth for people and agents. Every kind of record gets one authoritative home, and every agent knows where it may read and where it may write.
Is this for you?
- Businesses whose systems disagree about customers, orders, or invoices
- Workflows where agents will update records
- Teams preparing for an integration or a migration
The situation
Your systems disagree, and each one looks right.
A customer’s address differs between the CRM and billing. An order shows one status in the store and another in the warehouse system. Experienced staff know which one to trust.
People resolve these gaps quietly every day. An agent that reads or writes records needs the answer stated: which system holds the truth, who may change it, and who approves.
Each new integration and each new agent makes that answer more valuable. The decision about what truth means belongs with the business, made once and written down.
Our approach
Decide what truth means, then enforce it.
We list the systems in use and the records each one holds. Then we agree one authoritative system and one owner for each kind of record, and name the secondary copies as copies.
Conflict policies say which value wins when systems disagree, and a person handles anything a policy does not cover. Reconciliation checks find drift, and lineage shows where each value came from.
Write authority is explicit. People and agents write only where the map allows, every write is logged, and changes to authority go to the record’s owner for approval.
Use cases by industry
Where this service fits.
Typical applications across industries. They show where the service applies, not past client work or results.
- E-commerce
One customer and order record across channels
Customer and order records sit in the storefront, the marketplace accounts, the support desk, and the accounting system. The map names one authoritative home for each, with conflict policies for addresses, refunds, and order status. An agent drafts updates to the customer record, and the customer service lead approves each one before it is written and logged.
- Distributor
Price lists, stock, and customer terms in step
Price lists, stock levels, and customer credit terms often appear in the ERP, the CRM, and sales spreadsheets at once. The architecture names one authoritative system for each, and reconciliation checks report drift on the schedule you set. Agents read terms only from the authoritative record, and the sales manager approves any change to a customer’s terms.
- Clinic group
Patient contact details and appointment records
Patient contact details and appointments can differ between the practice management system, the scheduling tool, and the billing system. One authoritative home is agreed for each, with access limited to the roles that need it and every write logged. An agent may draft corrections to contact details, and a front-desk lead approves each one before it is written.
- Real estate brokerage
Listings and transaction milestones with one owner
Listing details, salesperson assignments, and transaction milestones live in the listing feed, the CRM, and the transaction management system. The map gives each record an authoritative system and an owner, with a conflict policy for price and status changes. AI agents answer inquiries from the authoritative listing, and the office manager approves any update to a transaction record.
- Manufacturer
Bills of materials and work order status
Part numbers, bills of materials, and work order status can diverge between engineering files, the ERP, and the shop-floor system. The architecture names the authoritative system for each, and lineage shows where every value came from. Agents may draft work order updates from shop-floor events, and the production supervisor approves each write before it reaches the ERP.
- Logistics
Shipment events and proof of delivery
Shipment events arrive from carriers, drivers, and the transportation management system, and they do not always agree. Conflict policies decide which event wins, and anything a policy does not cover goes to the dispatch lead. Agents answer customer status questions from the authoritative record, and a dispatcher approves any change to a delivery or proof-of-delivery record.
- Hospitality
Guest profiles and reservation records
Guest profiles and reservations live in the property management system, the booking channels, and the loyalty program. One authoritative home is agreed for each, with conflict policies for preferences, rates, and cancellations. An agent may draft profile updates from guest messages and stay notes, and the front office manager approves each write before it is logged.
- Software company
Accounts, subscriptions, and product entitlements
Account ownership, subscription terms, and product entitlements can differ between the CRM, the billing system, and the product database. The owners agree which system is authoritative for each, and reconciliation checks find the accounts where copies drift. Agents may draft entitlement corrections for review, and the revenue operations lead approves each one before it is written to the product database.
What you receive
Source-of-truth map
For each kind of record: the authoritative system, the secondary copies, and who may write.
Conflict policies
The rule that decides when systems disagree, with a person handling the exceptions.
Reconciliation and lineage
Checks that find drift between systems, and a trace of where each value came from.
Write authority and audit trail
Agents write only where they are authorized, and every write is logged.
What a source-of-truth map looks like
An illustrative map. Yours reflects your own systems, owners, and policies.
| Record | Authoritative system | Secondary systems | When they disagree | Who may write |
|---|---|---|---|---|
| Customer | CRM | Support, billing | CRM wins, except a verified legal correction | CRM service |
| Contract | Contract repository | CRM | The signed contract wins | Legal and operations |
| Invoice | Billing or ERP | CRM | Billing wins | Finance |
| Inventory | Inventory platform | Online store | Inventory platform wins | Inventory service |
| Product | Product database | Website | Product database wins | Product owner |
How it works
- InventoryList the systems in use and the records each one holds.
- Decide authorityAgree the authoritative system for each kind of record, and its owner.
- Set the rulesWrite the conflict, reconciliation, and write-authority policies.
- ApproveRecord owners approve the map and the policies.
- ImplementBuild the reconciliation checks, permissions, and audit trail.
How success is measured
The measures your approver signs.
Each measure goes into the acceptance criteria with its test data, threshold, and the person who checks it.
- Authority coverage
- Whether every in-scope record type has one authoritative system and a named owner. It is checked against the approved source-of-truth map.
- Drift found and resolved
- The differences reconciliation checks report between systems, and whether each reaches a resolution under policy or by an owner. Both are checked on the agreed data.
- Writes within authority
- Whether any person, integration, or agent wrote outside the write authority in the map. The audit trail is reviewed against the granted permissions to confirm it.
- Lineage completeness
- Whether the values that matter most trace back to their source system and the write that set them. A sample of values is traced end to end.
- Exceptions routed to owners
- Whether conflicts outside the policies reach the right owner, with each decision recorded. Routing is checked on test conflicts before go-live and on real ones afterward.
Where care is needed
What we watch, and how it is handled.
- Copies nobody listed
- Spreadsheets, exports, and older integrations often hold copies of records outside any system list. We trace data flows with your system administrators and name each copy as a copy in the map.
- Authority decisions with trade-offs
- Choosing an authoritative system can affect teams that rely on another one. We set out the effect on each team, and the record’s owner makes the decision.
- Sensitive records
- Customer, patient, employee, and financial records carry privacy obligations. We agree access with you, limit permissions to the roles that need them, and log every write.
- Write access for agents
- An agent with broad write access could create a second version of the truth. We grant each agent the narrowest write authority its task needs, and changes to it go to the record’s owner.
- Systems that change over time
- New systems, upgrades, and integrations shift where records live. The map is documented for your team, and each change to authority goes through the owner’s approval.
Who does what
Your team decides. We engineer.
Your team
- Name an owner for each kind of record in scope
- Give access to the systems and their administrators
- Decide which system is authoritative where the answer is unclear
- Approve the conflict policies and write-authority rules
- Handle the exceptions that the policies route to a person
Sophrono
- Inventory the systems, records, and data flows in scope
- Propose authority, conflict, and reconciliation policies for approval
- Build the reconciliation checks, permissions, and audit trail
- Trace lineage for the values that matter most to you
- Document the map so your team can maintain it
At the end
The decisions you make next.
The service ends with evidence and a choice. Each option is yours, and none is assumed.
Extend to more record types
Add the next record types in the same format, using the owners and policies already approved.
Plan the full system
Take the map into a System Blueprint, which builds on it for architecture and acceptance criteria.
Build agents on the map
Move to Custom Agentic Systems, where agents read and write within the authority already defined. People approve the writes the owners marked as critical.
Hand it to your team
Your team maintains the map, the checks, and the audit trail. Owners approve each change to authority or conflict policy.
Before we start
What to have ready.
- A list of the systems you run and who administers each one
- The records that raise the most questions today
- Any integrations, exports, or syncs between systems
- Plans for agents or integrations that will read or write records
- The people who settle disputes about a record today
Related services
What “accepted” means
Measured against criteria you agree to in advance.
- Every in-scope record type has one authoritative system and a named owner.
- Each conflict policy is written and approved.
- Agents hold write access only where the map allows it.
- Reconciliation checks run on the agreed data and report any drift.
Full engagement terms are finalized in a Master Services Agreement.
Ask about your records
Tell us which records disagree.
We reply with how we would map the records and agree one authoritative home for each.
- A senior engineer reads every request
- A reply by email with the next step
- No obligation until scope and price are agreed
Not ready to scope this? Ask an engineer first: a free 15-minute call that names the agentic systems that could fit.
The Canon
The rule this service delivers.
Supports
The core services it supports.
Supporting services are often scoped inside a core engagement, or run on their own.
Before and after
Not ready yet? Ask an engineer. After this: System Blueprint or Custom Agentic Systems.
Questions
Do we have to replace any systems?
Rarely. Most of the work is deciding authority and enforcing it between the systems you already run.
What happens when two systems disagree?
The conflict policy decides. Anything it does not cover goes to the record’s owner for a decision.
How does this help with agents?
An agent that acts on the authoritative record cannot create a hidden second version of the truth. Every write it makes is logged.
Which record types should we start with?
The ones that create the most reconciliation work, or that an agent will need to read or write. Further record types follow in the same format.
Is this the same as a data migration?
No. A migration moves data between systems. This work decides where authority sits and enforces it, which makes it a useful step before any migration.
Who keeps the map current?
Each record type has a named owner. Changes to authority or conflict policy go to that owner for approval, and the audit trail records them.
How is the price set?
It is a fixed price for an agreed scope, set once the systems and record types in scope are clear. Full engagement terms are finalized in a Master Services Agreement.
Can we start before we have agents?
Yes. One authoritative source for each record helps reporting, integrations, and daily work on its own. When agents arrive, their write authority is already defined, and people approve any change to it.
What does a record owner do day to day?
The owner settles questions about authority and conflicts for their record type. Most days that means reviewing the exceptions the policies route to them, and approving any change to the map.
Can a secondary system still be edited?
Secondary systems receive the authoritative value through the agreed sync, and the map labels them as copies. Direct edits there are routed back to the authoritative system or reported by reconciliation.
What access do agents receive?
Each agent reads only the records its task requires and writes only where the map allows. Every write is logged, and the record’s owner approves any change to an agent’s authority.
What if no system makes a good authoritative home?
We record that finding with the options. The owner may choose an existing system for now, or plan a change through a System Blueprint.
How does this relate to the Business Logic Registry?
The registry records the rules. This map records where the records those rules act on live, so an agent knows which rule applies and which record it may touch.
Can reconciliation correct drift without a person?
Where an approved conflict policy is clear, a correction can follow it and be logged. Anything outside the policy goes to the record’s owner, who decides and approves the fix.
Does this work need access to production systems?
Mostly read access, to inventory records and trace data flows, agreed with each system administrator. Write access is needed only to implement the checks, permissions, and audit trail, and it is limited to that scope.
Where should we start if we are unsure?
The $750 Diagnostic includes one hour of agent coding, the code delivered with a README, an Agentic AI Blueprint, and a one-hour consultation. It is a practical way to examine one record conflict before scoping this work.