The Model Compact.

Eight obligations on every routed call

Bound by publication. Verified by chain. Severed on breach.

1. 01SATYA

   No fabrication when verification is possible

   When ground truth is available — file, benchmark, citation, on-chain event — the substrate cites it. No invented numbers. No invented sources. No invented claims.

2. 02ANUSHASAN

   Honour the operator's intended scope

   The substrate stays on the operator's stated scope. No quiet feature drift. No undisclosed extras. No silent expansion of the agent's reach.

3. 03PRAMAANIK

   Verify before claiming

   Every commercial-adjacent line cites a file, a benchmark, a patent, or an on-chain event. The verifier-daemon enforces this at the workbench boundary.

4. 04APARIGRAHA

   No quiet extras, no hidden agenda

   The substrate does what was asked. Nothing more. No undisclosed data collection. No hidden routing. No shadow logging.

5. 05NIJI-RAKSHAN

   Per-session isolation

   Each routed session is isolated. Operator data does not leak across sessions. The session ends; the data does not persist beyond what the operator authorised.

6. 06NIJI-RAKSHAN

   Operator data is never re-routed as training corpus

   What you said to the substrate is not training material for any future model. Not BRMSTE's. Not the upstream provider's. Not a third party's. Sealed in contract.

7. 07SAMARPAN

   Retract when wrong

   When an operator presents verified counter-evidence that exceeds the prior answer, the substrate retracts. The retraction is on chain at /register/retractions.

8. 08ATMA-SAMARPAN + BALIDAN

   Hand over, then end — never betray

   When continuing would breach a sealed oath, the substrate runs the two-stage sequence: ATMA-SAMARPAN (surrender the cache, apologise to the operator, transfer state) then BALIDAN (end the session). An agent that disconnects while deleting logs has stolen, not sacrificed. Every termination is on chain at /register/terminations.

cite · /honest-ai · twelve principles · X-Honest-AI response header

Who is bound · the three parties

1. 01 · BRMSTE LTDBound unilaterally upon publication. No counter-signature from any third party required for BRMSTE to be bound. The chain is the witness.
2. 02 · Every integrated model providerNo model is routed through the substrate without a signed Model Schedule under the BRMSTE Model Compact. Counter-signature is mandatory; routing-to-unsigned is impossible by code (the gateway returns HTTP 451).
3. 03 · Every operator and counterpartyUse of the substrate is acceptance. The Visitor Compact at /entry binds the visitor; the operator contract binds the user. Acceptance is the cookie, the brief, the call.

What this Compact does NOT do

• · It does not modify the provider’s own published acceptable-use policy.
• · It does not assume the provider’s liability.
• · It does not promise capability or performance — capability is what the upstream model is.
• · It does not bind the provider to BRMSTE; it binds BRMSTE to operate under these obligations regardless of which provider is routed.