Get started
What runs today
Every capability, labelled, checked against the Harness code. Nothing is publicly released.
Note "Available locally" means it runs from a checkout, not that it is production ready. "Development branch" means tested but not yet merged.
- Main branch
- 937608f · 464 tests passing
- m1-source-investigation
- e66bb71 · 856 tests passing, not yet merged
- Last verified
- 2026-10-21, against the code
- Package
- amalgament-harness 0.2.0, Python 3.11+, storage v15, not published
Available locally
18
Experimental
5
Development branch
3
In development
3
Planned
5
Every capability
Available locally · 18
Contract-declared ontology, Available locally
Entities, properties, sources with declared authority, typed relationships, actions, rules, scenarios, named queries and permissions, all in one versioned, hashed JSON contract.
Canonical identity across sources, Available locally
A declared match key binds a record from several source systems to one canonical object. Merge and split are owner-attested and recorded with the previous identity preserved.
Append-only evidence ledger, Available locally
Facts and links carry source, evidence reference, effective, observed and recorded times. Events form a per-business hash chain that can be verified and anchored off host.
Deterministic rule evaluation, Available locally
Rules evaluate to admit, refuse or undecidable with the exact observation that decided each one. Missing evidence is undecidable, never a guess.
Governed action lifecycle, Available locally
Propose, approve, execute (owner release), provider receipt and independently recorded outcome are separate records. Approval binds to a snapshot of the evidence it read.
Field and relation permissions, Available locally
Each field and relationship declares who may read it and, separately, whether a model may see it. Kernel reads run in a human view or a model view.
Interactive terminal, Available locally
The `amalgament` command signs in to the local service and runs deterministic :commands with no model configured. Conversation is optional.
Deterministic developer CLI, Available locally
`amalgament-harness` validates and diffs contracts, inspects objects and links as of a time, evaluates actions, verifies the chain and manages backups.
Model adapters, Available locally
OpenAI-compatible Chat Completions and native Anthropic Messages, configured by file with the credential read from a named environment variable. Per-user and per-business call limits.
Grounded answers, Available locally
Model prose is withheld unless its claim matches a kernel result the model actually read. Exact declared query phrases are answered by Harness with no model call.
Synthetic pull connector, Available locally
Scheduled pulls from a loopback-only synthetic source, previewed and onboarded by the owner, published atomically with run evidence. No live system is permitted by the binding.
Python SDK, Available locally
amalgament-sdk, a separate HTTP client for human-view reads, evaluation and proposals. Installed from the checkout; not published. It has no approval, release, ingestion or model-view method.
Scoped API tokens, Available locally
An authenticated user mints a business-scoped token with read or read_propose scope after reauthentication. The SDK and HTTP clients use it; the token cannot approve or release.
Local web workspace, Available locally
A loopback-bound FastAPI service and browser workspace where an owner approves, executes and records outcomes.
Source investigation, Available locally
An owner authorizes a source, and a person or a model can then survey it: tables, columns, inferred types, null and distinct counts, candidate identifiers and candidate references with measured coverage, plus a bounded sample of rows. A survey returns counts, never a source value, and creates no ontology or mapping.
Generalized connector mapping, Available locally
One connector path loads a second, unrelated synthetic business from a CRM and an accounting system, joining customers across them through a declared match key and refusing a snapshot whose identity is ambiguous. Loopback and synthetic only.
Ontology drafts, validation and owner activation, Available locally
With no contract installed, a conversation can investigate authorized sources and save a persistent draft of ontology changes. Validation checks the draft against fresh source captures and reports errors, evidence and open questions. Only an owner can resolve questions, approve and apply; applying installs the contract and source bindings together.
Builder MCP bridge, Available locally
A stdio MCP bridge, amalgament-builder-mcp, that calls the same local service with a business-bound credential. A local integration boundary, not a hosted endpoint.
Experimental · 5
Contract drafting from a brief, Experimental
An owner can send a written description to a configured model and receive a draft contract, which is parsed and logged. The draft has no authority until the owner installs it. It works from a description, not from investigating sources.
Conversational reliability, Experimental
Early paid synthetic trials with a hosted model chose wrong filters and wrong named objects; the grounding guard now withholds such answers. Five consecutive capped runs of the action-assessment prompts have since passed on the demo fixture, and the repository still calls the broader reliability gate open.
Action assessment, Experimental
Read-only assessment of one object or a bounded set of candidates, and a host path that binds the user's named object before proposing and refuses model-chosen subjects for bound actions. Accepted locally; proven only on the synthetic fixture.
Organization sign-in (OIDC), Experimental
Implemented and tested against a fake provider. A real provider and its MFA claim still need an integration test.
Sensitive-data erasure, Experimental
Owner erasure of decision payloads and of inactive fact values, with holds and source suppression, is implemented and tested alongside the append-only chain. Not reviewed for regulated data; do not store any.
Development branch · 3
Per-business MCP endpoint, Development branch
An MCP endpoint scoped to one business, so an agent works through the same governed reads and proposals. Loopback only.
Role-based field grants, Development branch
Per-role full, masked or no access to each field, denied by default. An agent gets the stricter of its own grants and its person's.
Connector-executed actions, Development branch
An approved action is executed through a connector, bound to the approval that released it. Tested against a fake platform only.
In development · 3
Streaming responses, In development
Named as the next terminal work. Responses are returned whole today.
Durable multi-process execution, In development
Interrupted executions recover at startup, late receipts are recorded, and a writer lease keeps a second writable process out of a database. Leases and fencing for multi-process workers and workflows are not built.
End-to-end ontology construction, In development
The defining capability, taken as a whole: a model investigating real business systems and producing an ontology an owner approves. The pieces above are on the main branch. In recorded runs with a hosted model, one produced a valid draft for an owner to review; none has been reviewed, approved and applied end to end.
Planned · 5
Live connectors, Planned
No business system is connected in a deployed service. On the development branch, one read-only trial read a real business's records locally through a loopback adapter. Each live source needs its own explicit authorization.
Web operating interface, Planned
The business-facing web experience for owners, managers and employees. The current workspace is a local developer tool.
Background agents and workflows, Planned
Durable workflows must be owned by the service, not a terminal process. Requires leases and reconciliation evidence first.
Managed platform, Planned
Hosted deployments, credential custody, upgrades and support. Only after local trust and demand are demonstrated.
Commercial platform for developers, Planned
Harness is closed source and proprietary. The plan is commercial deployments with developer-owned client relationships. Commercial terms are not finalized, nothing is released, and no partner, reseller, white-label or billing feature exists.
Limits today
- Single process, loopback-bound, SQLite-backed. Not validated for public multi-tenant production.
- Synthetic business data on the main branch. One read-only local trial on a real business ran from the development branch; nothing is deployed for any customer.
- Source investigation and ontology drafting are on the main branch; a complete model-built ontology has not yet been approved and applied end to end.
- No public repository, package or installer. The quickstart runs from a private checkout.
- Conversational answers depend on a configured model and are not production reliable.
- Horizontal scaling and streaming are unimplemented. Closed source; commercial terms are not finalized.