From 6eba68706697dc5e2db98853963e51a984757292 Mon Sep 17 00:00:00 2001 From: blocksifrdev Date: Tue, 15 Sep 2026 13:00:00 -0400 Subject: [PATCH] Add the required public messaging (#47) Issue #47 lists messaging the repository was required to carry, and none of it appeared anywhere: not "Your AI has credentials. BlockSiFr gives it boundaries", not "Same identity. Same permission. Different consequence. Different decision", not BlockSiFr Control, Execution Control Infrastructure, Consequence Intelligence, the January 6 2027 launch date, the early-access line, or the CTA. The issue also records why it was never applied: repository rules blocked the automated commit. Those rules were scoped to main and unblocked earlier today, so it lands now. It sits below the quickstart rather than above it. A visitor arriving at an open-source repository is there to find out whether the thing runs, and the commercial framing reads better once they have seen that it does. The naming also goes into COMMERCIAL_BOUNDARY.md, where someone looking for the open/commercial line will actually look. Co-Authored-By: Claude Opus 5 --- README.md | 16 ++++++++++++++++ docs/COMMERCIAL_BOUNDARY.md | 10 ++++++++++ 2 files changed, 26 insertions(+) diff --git a/README.md b/README.md index 91bd35f..b5f2aaf 100644 --- a/README.md +++ b/README.md @@ -60,6 +60,22 @@ No account, no network: everything stays in `./pctr.json` and `./.pctr`. Three f PCTR routes to the consequence. TTP binds the authority for the exact execution that reaches it. +## BlockSiFr Control + +> **Your AI has credentials. BlockSiFr gives it boundaries.** +> +> Same identity. Same permission. Different consequence. Different decision. + +**BlockSiFr Control** is the commercial product for production enforcement, in the +**Execution Control Infrastructure** category, powered by **Consequence Intelligence**. +TTP and PCTR are the open protocol layer beneath it, Apache-2.0, and stay that way — see +[NOTICE](NOTICE) for the royalty-free grant. + +**Public launch: January 6, 2027. Early access is open now** for organizations, builders, +design partners and strategic partners: [hello@blocksifr.com](mailto:hello@blocksifr.com). + +**Put an action under Control.** + ## Under the hood: the Trust Transfer Protocol **TTP is the open protocol for machine chain trust:** proving whether the chain behind an AI agent, copilot, workflow, pipeline, API, service account, or non-human identity is trustworthy enough to be relied on, before downstream authority and execution decisions occur. diff --git a/docs/COMMERCIAL_BOUNDARY.md b/docs/COMMERCIAL_BOUNDARY.md index 5c674bb..9e87449 100644 --- a/docs/COMMERCIAL_BOUNDARY.md +++ b/docs/COMMERCIAL_BOUNDARY.md @@ -45,3 +45,13 @@ Execution Exchange enforces downstream runtime decisions in production. CortexTrace records and verifies execution evidence and receipts. Commercial use of BlockSiFr-managed services, proprietary adapters, production enforcement infrastructure, compliance exports, production receipt ledgers, and enterprise control-plane capabilities requires a commercial agreement with BlockSiFr. + +## Naming + +- **BlockSiFr Control** — the commercial product for production enforcement. Category: + **Execution Control Infrastructure**. Core intelligence: **Consequence Intelligence**. + Public launch January 6, 2027; early access open now. +- **TTP** and **PCTR** — the open protocol layer beneath it, Apache-2.0. +- **Execution Exchange** — the enforcement component in the architecture documents, and a + BlockSiFr trademark. Not the customer-facing product name. +- **FrontDesk** — legacy. Not for customer-facing material.