Build
Framework adapters and connectors
Domain architecture adapters for ingesting professional knowledge, execution connectors for reaching enterprise systems, and the permissions that separate them.
Two interfaces that must not be confused
| Class | Purpose | Typical sources or targets |
|---|---|---|
| Domain architecture adapters | Ingest and structure authorised professional knowledge while a framework is being built. | Procedure manuals, competency models, role and hierarchy maps, decision trees, permitted interview records, process diagrams. |
| Execution connectors | Let approved Engine tools interact with specific enterprise systems at runtime, under customer authorisation. | ERP, accounting ledgers, CRM, identity, document stores, issue trackers, code repositories, approved banking and government interfaces. |
Ingestion happens during development. Execution happens on a customer site. They carry different permissions and are never granted together by default.
Provenance
Every ingested source and every rule derived from it keeps a provenance record: what it came from, who authorised it, which version it belongs to, and who reviewed it. A rule with no provenance cannot be promoted.
Safety rules
- No unrestricted source ingestion.
- Secrets are never embedded in package code.
- Outbound interfaces require explicit customer approval and a network mode that permits them.
- Cross-vault data use is prohibited without a separately authorised data-flow design.
- Air-gapped sites require signed offline bundles.
Operating an adapter service gives a publisher no access to customer vaults.