Company Overview · Chapter 2
The Foundation
Records hold the facts. Operating knowledge, organized as the AI layer, supplies the definitions, instructions, roles and rules. Together they support the outputs a client chooses.
Four fictional worked examples show how the two foundations combine. Open any example for its filled sample and acceptance check.
Facts, Meaning And Decisions
How The Two Foundations Work Together
- Foundation 1 · Records Hold The FactsWhat happened and when: the job, the inquiry, the admission event or the invoice.
- Foundation 2 · Knowledge Supplies The MeaningDefinitions, instructions, roles and rules, organized as an AI layer that people and AI both use.
- People Make The DecisionA named client owner validates the meaning and decides what happens next.
Four Worked Examples
See The Foundations Work Together
Each example uses fictional, illustrative facts. None describes a live installation or a client result.
- Fictional Example · Two Foundations
Two Foundations, One Working Business
- Foundation 1 · Facts
- Job J104: field complete, signoff missing.
- Foundation 2 · Meaning
- Rule v2: signoff before invoice review.
- Result & Owner
- Awaiting Signoff · Client Office Manager
Fictional Example · Why Context MattersFrom Raw Counts To Useful Decisions
- Foundation 1 · Facts
- Five source inquiry rows, Q1–Q5.
- Foundation 2 · Meaning
- Unique inquiry ID, received Oct 1–7, qualified.
- Result & Owner
- 2 Qualified Inquiries · Client Sales Manager
Fictional Example · Connected DepartmentsOne Relationship, Different Department Views
- Foundation 1 · Facts
- R07, INQ27, ADM09 and INV12, each with its own date.
- Foundation 2 · Meaning
- Shared IDs plus a BD playbook, admissions SOP and billing rules.
- Result & Owner
- One Handoff Register · BD, Admissions And Billing Leads
Fictional Example · Existing ToolsConnected To The Tools You Use
- Foundation 1 · Facts
- CRM inquiries and a job spreadsheet stay in place.
- Foundation 2 · Meaning
- Approved SOP v2 is current; draft v3 is excluded.
- Result & Owner
- Proposed Source Map · Client Source Owners
Same Meaning Across Teams
Departments share the IDs and definitions coordination depends on, such as an inquiry, an admission event or an invoice. Each role keeps the playbook, SOP or rules its own work needs.
See One Relationship Across Departments →Built Around Existing Tools
A CRM, spreadsheet, document library or EMR can keep doing its current job. BH Tech maps which source holds each field and who keeps it current. A connection is relied on only after permission, mapping, testing and handover.
See A Proposed Source Map →Build Only What The First Result Needs
There is no mandatory migration or single database vendor. BH Tech organizes only the records and operating knowledge the agreed first result needs, with a named client owner and an acceptance check.
See Where Work Starts →Twelve Categories
What Each Foundation Holds
Open any category for its infographic and example. A client uses only the categories its first result needs.
Foundation 1 · Records & Data
Foundation 2 · Operating Knowledge As An AI Layer
See All Twelve Categories Working Together →