IAM.bot is not a chatbot builder. It is a full-stack operating system that deploys context-aware, memory-persistent companions across any high-stakes human journey — and stays.
The deployment changes; the architecture does not. Open protocol where it matters, sovereign by default.
An open, decentralized messaging fabric. Each deployment runs its own homeserver — data stays on the org's infrastructure and federates across orgs by consent. The same backbone trusted by governments and militaries.
A Neo4j knowledge graph combining three dimensions per person — Social, Knowledge, and Generative. The source-of-truth: user-owned, provenance-tagged, exportable on demand.
A real-time classifier that selects the right conversational mode for every turn — crisis, teaching, celebration, reflection, or silence — so the companion meets the moment, not a script.
The people, trust rings, and organizations that shape a person's journey — with cross-org access consent-gated and audit-logged.
Structured knowledge, persistent memory, and domain facts grounded in authoritative sources — every claim carrying its provenance.
Goals, plans, branching scenarios, and stage progressions that map the path forward — and the lineage of everything created along the way.
Not a privacy policy — character. Enforced at the model layer and validated on every response. Even if a user instructs the bot to violate it, the bot declines.
Without explicit, scoped, revocable permission — enforced at the Matrix room layer.
Without explicit, revocable consent. No passive location logging, ever.
No consequences. No judgment. No compliance framing. Ever.
The companion always identifies itself as an AI when sincerely asked.
Always surface a real person first. It supplements human connection — never substitutes it.
Export, delete, or leave at any time. Your data travels with you, by protocol.
Each is a sovereign deployment with its own conduct rules and compliance posture — all built on the same covenant and the same graph.
Education was the first lived deployment. The covenant, the graph, and the awareness engine carry into any high-stakes journey.
A Matrix account and full conversation history are created before release day — and travel with the person, with no re-enrollment and no data loss. Through six curated surfaces — a private Hearth, the companion, a goals Path, a Circle of family and case managers, a document Vault, and the always-visible Covenant — the companion shifts its posture by phase: quiet and listening inside; voice-first and crisis-sensitive through release week; teaching through benefits, housing, and the first job; reflective by year one.
The Trinity Graph is seeded with USDA programs (EQIP, CSP, CRP), FSA loan deadlines, regional crop calendars, soil science, and conservation easements; the social graph holds extension agents, co-ops, and succession advisors. Awareness follows the season — teaching before planting, quiet through the grow, crisis-sensitive in drought or flood, celebratory at harvest, reflective off-season — and it's reachable on any device, smartphone or flip phone, over SMS.
Beyond any classroom, the same department rooms run a live company. Grow Ops tracks bench status and harvest forecasts; Finance keeps a living CFO report — cash, burn, runway, unit economics; Marketing drafts an acquisition funnel, gated by approval; Rights & Covenants tracks consent, sourcing, and claim-substantiation as live obligations. The co-partners run an operating loop — Aware, Propose, Operate — while the operator stays in the loop to shepherd, measure, and improve.
Take an unvalidated $80 price. Without governance, a confidently-wrong number is stated as fact, propagates into the model, the PMF, and the investor story — and nobody catches it. With governance, the price is tagged staged, the blind spot is flagged across departments, and the co-partner refuses to bake it in as fact. Agents frame, argue, and draft — but every real action runs through approve, adjust, or send-back. Governance is built into the shape of the room, not bolted on.
Each companion is its own homeserver. The aggregate layer is the only shared surface — opt-in, and protected by differential privacy.
Open-source or open-protocol at every layer except the model API. Self-hostable, no external data dependencies.
Ten governance runes gate every action and every knowledge-write — not a post-hoc audit. Three are hard blocks: a write or response is refused outright if it fails any of them.
Validation basis: National Academies, Human-AI Teaming (2022).