The claims, each with its state and its sources.

outboundfix.io is live. It presents OutboundFix as Commercial Decision Infrastructure, publishes the entry offer of ten real accounts, and states for each access surface whether it is available, implemented or not yet active.

• Read by GET on 2026-10-05: https://outboundfix.io/ returned 200; the category, the promise and the ten-account offer are on the page
• Repository: OutboundFix public truth module
• Merged change #261 (be30b1b7): Public positioning reconciliation

Each account whose research completes receives PASS, RESEARCH_MORE or KILL, written as an immutable decision record with its evidence. AI gathers evidence; it never decides. When research fails or a claim cannot be verified, the outcome is never a PASS or a KILL.

• Repository: OutboundFix public truth module
• Repository: OutboundFix decision core package

The web workspace is deployed and serving. It is not yet validated in production.

• Repository: Public positioning reconciliation record
• Merged change #259 (67a01589): Workspace on the governed decision core

The API, the MCP server and the CLI are implemented on the same governed decision boundary and return the same verdicts. All three are switched off in production: the service refuses every request to them.

• Merged change #249 (c2954cd2): Headless access
• Repository: OutboundFix public truth module

A HubSpot decision loop with human approval before any write-back, and a Clay intake that sends enriched accounts for a decision, are built and tested. Neither is enabled in production.

• Merged change #248 (5520bcb7): Clay integration
• Repository: OutboundFix public truth module

TerminalCor3's system of record for property acquisition and development separates preparing an action, approving it and executing it. Twelve classes of consequential action need a recorded human approval: paid registry research, paid technical due diligence, an outside adviser engagement, owner outreach, a broker engagement, lender outreach, investor or joint-venture outreach, an indicative offer, a letter of intent, exclusivity, an acquisition commitment and a capital commitment. None is executed automatically: this version has no executor.

• Repository: TerminalCor3 gated action types
• Repository: TerminalCor3 human gate
• Repository: TerminalCor3 execution boundary

The public site terminalcor3.com is live.

• Read by GET on 2026-10-05: https://terminalcor3.com/ returned 200

Energy infrastructure, data-center power and compute-ready power are the direction TerminalCor3 is working toward. Nothing in that direction is built or deployed.

• Repository: Locked direction of this site

A stateless MCP server exposes four tools: analysing a public tender notice, evaluating a commercial policy, calculating landed cost and comparing bill-of-material options. Each returns a bounded outcome: a tender analysis ends in PASS, RESEARCH_MORE or REJECT, a policy evaluation in ALLOW, DENY or ESCALATE, and a landed cost is labelled verified, estimated or unknown.

• Merged change #241 (8f1aa1e8): Brisora MCP server
• Repository: Brisora MCP server source
• Repository: Brisora MCP implementation report

The public site brisora-trade.com is live.

• Read by GET on 2026-10-05: https://brisora-trade.com/ returned 200

No public endpoint is published for Brisora. The merged work is the server, its tests and demo material on public data.

• Repository: Brisora MCP implementation report

PCS takes a provider-neutral capture envelope through interpretation, planning, rendering and quality checks to a delivered piece. Its test suite includes real video renders.

• Repository: PCS product readme
• Repository: PCS Meta glasses final report

A Meta wearables adapter and an Android bridge are built; the bridge compiles. The end-to-end path passes with a synthetic bridge delivery and a real, quality-gated render.

• Repository: PCS Meta glasses final report
• Repository: PCS Android bridge readme

Nothing has run on physical Meta glasses or on Meta's mock device. Real hardware tested: no.

• Repository: PCS Android bridge readme
• Repository: PCS Meta glasses final report

One recorded example: a reviewer separate from the author reviewed one exact commit and returned changes required; the findings were closed in new commits, and the new head was reviewed again. That re-review left one wording finding, and the commit that closed it was merged after the re-review. The repository's record ends at the re-review: it holds no review of that last commit.

• Repository: Brisora MCP implementation report
• Merged change #241 (8f1aa1e8): Brisora MCP server

In one recorded check, 97 guards were each disabled or weakened in turn and the test suite was run against every mutant: 96 were killed and 1 survived, and the survivor is recorded with the result.

• Repository: Internal runtime reconciliation report

The internal authority contract defines nine classes of effect. Two can be authorized: read-only external access and internal durable writes. The other seven, including external communication, financial transactions and production deployment, are denied whoever asks.

• Repository: Internal authority contract

The internal authority store has run on a deployed database over verified TLS, in shadow mode. Restart, forced-kill recovery, writer takeover, halt and revocation drills passed there. Shadow means no live external effect is authorized, and the gate closed as a conditional pass.

• Repository: Deployed shadow pilot report
• Merged change #238 (638742f0): Deployed shadow pilot

This site sets no cookies, runs no JavaScript and loads nothing from another domain. Fonts are served from this domain, and a content security policy enforces the rest.

• Repository: This site's response headers