Source: frameworks/kit-reference-data/client-reference-data-template.md
CLIENT REFERENCE DATA
[Client Name] — [Company Name]
Created: [Date] | Last Updated: [Date] This document is the canonical source of truth for all proper nouns, team members, and tools referenced across Advisory OS agents. Upload this file to every agent project when processing this client. All agents override transcript/JSON spellings with this document.
Company
| Field | Value |
| Legal Name | |
| Common Name (if different) | |
| Industry | |
| Location / Time Zone | |
Team Roster
| Name (correct spelling) | Role | Notes |
| | |
Include: anyone who appears in sessions, constraint briefs, or will be named in builds. Flag transcript misspellings in Notes column so agents know what to override (e.g., "Transcripts render as 'Jennifer'")
Tools & Software
| Tool (correct name) | What it's used for | Transcript misspelling |
| | |
Example: Financial Cents | Practice management, workflows | "Financial Sense"
Key Proper Nouns
| Correct | Incorrect (from transcripts) | Context |
| | |
Catch-all for anything else that gets misspelled in audio-to-text: client names, vendor names, software features, industry terms.
Engagement
| Field | Value |
| Entry Point | |
| Current Engagement | |
| Rate | |
| Start Date | |
| Meeting Cadence | |
| Advisor | Kathryn Brown |
| Brand | Advisory OS |
Update Log
| Date | What Changed | Updated By |
| | |
USAGE RULES (for all agents)
- This document overrides all other sources for proper nouns — transcripts, JSONs, constraint briefs, matrix outputs. If a name appears differently in a transcript than in this document, this document wins.
- Upload to every agent when processing this client: IC System, Build Design Agent, AISOP Factory, QC Agent, Constraint Priority Matrix.
- Created during onboarding. Advisor fills this out before the first agent run for a new client.
- Updated when team changes. New hire, departure, role change, new tool adopted — update this document first, then re-upload to active agent projects.
- Layer 1 Reference section mirrors this document. When the IC system builds Layer 1, it pulls the Reference block from this file. They should always match. If they don't, this file is the authority.