Hyphos
Talk about a pilot

Architecture

The shape of how Hyphos works.

Enough to evaluate. Not enough to copy. We show you the architecture — the loop, the depths, the packages, the ontology, the provenance — without the internals that took us years to build.

1 · The loop

Four planes, running together.

Hyphos isn't a pipeline that runs once a day. It's four planes operating continuously, each feeding the next, closing back on itself. Below is what flows through each plane.

1

Capture

Inputs flow in from where the work already happens.

  • · Meetings — audio, transcripts, speaker turns, decisions named in conversation
  • · Documents — PDF, DOCX, XLSX, slide decks, structured forms, contracts
  • · Email & chat — threads, attachments, commitments made in passing
  • · Existing systems — CRM, ERP, scheduling, document repositories
  • · Prior deliverables — the work your team has already shipped
2

Structure

Inputs become a coherent knowledge object.

  • · One engagement object — the spine that everything else hangs off
  • · Shared ontology — what counts as a decision, a commitment, a risk, a deliverable, a stakeholder
  • · Knowledge graph — typed relationships between every entity in every source
  • · Provenance on every claim — back to the speaker, the section, the timestamp
  • · Versioned revisions — every artifact, every change, fully audited
3

Teach

Knowledge becomes scaffolded delivery to the team.

  • · Interactive HTML deliverables — explored, not read; the reader controls depth
  • · Developmental companions — facilitator guides, reasoning trails, watch-for-next-time
  • · Channel-native delivery — into email, meetings, chat, where the team already is
  • · Modeling, scaffolding, fading, articulation — the four moves of cognitive apprenticeship
  • · Mention · Ask · Articulate — every revision is named, chosen, and explained
4

Retain

Edits and corrections become captured craft.

  • · Living templates — mature with use; the next deliverable inherits the last one's learning
  • · Craft patterns — captured from your firm's actual edits, structurally
  • · Organizational memory — decisions, commitments, the say-do record
  • · Read-before-Edit discipline — every mutation re-grounded in the source
  • · Open export — your knowledge stays yours; nothing locked in

2 · The depth stack

Five depths of knowledge.

Knowledge isn't one thing. The wisdom of a master practitioner, the conventions of your industry, the house style of your firm, and what's happening on this engagement right now are all different depths. Hyphos captures and uses each, distinctly.

5

Live signal

This week · this meeting · this hour

What was just decided · who said what · the commitment made in passing · the risk surfaced and not yet captured · the change in client mood

4

Engagement

This project · this matter · this case · this deal

Scope, schedule, cost, quality, resources for this specific work · the stakeholders · the deliverables produced · the decisions made · the commitments outstanding

3

Organization

Your firm · across engagements · over years

Your house style · your conventions · your seniors' craft · your firm's decision patterns · the way you produce a proposal, a plan, a report, a brief

2

Industry

Your sector · regulatory · conventional

Industry-specific ontology · standard document types · regulatory references · sector-conventional deliverable structures · the patterns that work in your vertical

1

Universal

How knowledge work works · across all organizations

Cognitive apprenticeship patterns · mature deliverable structures · decision frameworks · the craft of how complex work compounds · what all good firms quietly do

When Hyphos produces a deliverable or answers a question, it pulls from each depth as appropriate — and tells you which depth informed which part of the output.

3 · Knowledge packages

Industry packs that ship pre-shaped.

You don't start from scratch. Hyphos ships with industry-specific knowledge packages — pre-shaped ontology, starter templates, regulatory references, and stakeholder models for the verticals we know deeply. New packs are built one industry at a time, in partnership with the firms in that vertical.

Construction & Capital Projects

Live

Owners, contractors, engineering firms, capital program teams

  • · Project lifecycle ontology
  • · RFI, change order, submittal flows
  • · PMIS integration patterns
  • · Document-control governance

Professional Services

Next

Consulting firms, advisory practices, engineering services

  • · Engagement lifecycle ontology
  • · Proposal · deliverable · report patterns
  • · Time-and-billing integration
  • · Practice-area shaping

Legal & Compliance

Planned

Law firms, in-house counsel, compliance teams

  • · Matter lifecycle ontology
  • · Privilege and confidentiality model
  • · Regulatory references
  • · Document precedent libraries

Financial Advisory

Planned

Wealth, planning, family office, fiduciary practices

  • · Client relationship ontology
  • · Plan · review · recommendation patterns
  • · Regulatory references
  • · Stewardship documentation

Healthcare Operations

Planned

Clinical operations, practice management, care coordination

  • · Case lifecycle ontology
  • · Privacy-first capture
  • · Regulatory references (HIPAA, etc.)
  • · Multi-disciplinary stakeholder model

Yours

Custom

Specialty trades, family law, estate planning, property management, manufacturing operations — and more

  • · Custom ontology shaped to your work
  • · Templates seeded from your existing deliverables
  • · Integrations with your systems
  • · Built with you in the pilot

Don't see your vertical? We build packs as engagements demand them. Tell us what you do.

4 · The shared ontology

One vocabulary across every source.

A commitment named in a meeting and a deliverable due date in a contract are the same underlying object. Hyphos has a shared vocabulary — an ontology — that recognizes that, so the knowledge graph isn't a heap of unconnected mentions. It's a coherent picture of your work.

What the ontology recognizes

  • ↦People — role, authority, expertise; never personality or behavior
  • ↦Decisions — who decided what, when, on what basis
  • ↦Commitments — what was promised, by whom, by when
  • ↦Risks — what could go wrong, who raised it, what's being done
  • ↦Deliverables — what's being produced, for whom, due when, in what state
  • ↦Changes — what changed, why, who authorized, what's affected downstream
  • ↦References — contracts, regulations, prior deliverables, standards
  • ↦Engagements — the unit that ties scope, schedule, cost, quality, resources

Why it matters

Without a shared ontology, every source is its own island. A meeting transcript says "Sarah will get back to us by Friday" — that's one mention. A contract clause says "Vendor shall deliver by EOW" — that's another. A task in your project tool says "Sarah · Friday · vendor response" — a third.

The ontology recognizes these as one object — one commitment, with three independent signals confirming it. When Sarah doesn't deliver, Hyphos knows immediately. When the contract changes, Hyphos knows what else is affected. The knowledge graph stays coherent because the vocabulary is shared.

Industry-shaped, organization-tuned

The base ontology is universal — these concepts exist in every organization. Industry packs add domain-specific objects (an RFI in construction, a matter in legal, a clinical case in healthcare). Your organization tunes both — adding your firm's specific document types, role conventions, and decision frameworks during the pilot.

5 · Open by design

Bring your own AI client.

Hyphos isn't another walled garden with its own chat UI you have to learn. It speaks the open standard your team's AI tools already speak — so the people who already work in Cursor, Claude, ChatGPT, or a custom internal client can query the knowledge graph from inside their existing surface.

What MCP is

Model Context Protocol is an open standard (originated by Anthropic, now adopted broadly) for connecting AI clients to data sources. Think of it as USB for AI tools — one protocol, many clients, many sources.

Hyphos publishes an MCP server. Any compliant client can connect to it and query your organization's knowledge graph, retrieve documents, ask about decisions, surface provenance, or trigger deliverable generation — without leaving the tool the user is already in.

What this means for your team

  • ·No tool switching. Seniors who live in Cursor stay in Cursor. Partners who prefer Claude Desktop stay there.
  • ·Same access rules. Role and attribute-based access apply at the MCP layer. A junior asking a question gets what they're allowed to see; a partner gets more.
  • ·Full provenance. Every answer the MCP server returns carries pointers back to source — speaker, document, timestamp.
  • ·Audit trail. Every query is logged. Who asked what, when, what came back.
  • ·No lock-in. MCP is open. If a new client comes out tomorrow, it just works.

We also publish a web assistant that runs against the same MCP server — for users who don't have an MCP client of their own, or want a browser-native experience without any setup.

6 · Provenance & trust

Every claim, traceable. Every layer, transparent.

Full provenance on every claim

When Hyphos says something, it shows you the source — the speaker, the section, the timestamp, the document, the decision. No black boxes. Every answer can be drilled down to its origin in seconds.

Customer-specific knowledge stays in your partition

Your deliverables, meetings, decisions, edits — all stay in your organization's partition. Role and attribute-based access control inside. No cross-customer leakage of the work itself.

Cross-customer learning is anonymized and named

The platform improves over time by learning structural patterns at the craft layer — and we tell you exactly what's learned. Anonymized only: names, companies, projects, locations stripped before any cross-customer use. Enterprise can opt out entirely.

Open export, no lock-in

Your knowledge graph, your captured craft, your deliverables — exportable in open formats. If you ever leave, you take everything that's yours with you. The platform is the loop; the knowledge is yours.

Architecture is one thing.
Seeing it on your work is another.

The fastest way to understand whether Hyphos is the right shape for your organization is to put it next to a real engagement of yours and see what comes out. Pilots are scoped one at a time.

Talk about a pilot See pilot shapes