You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pulls fresh content from stackbilt-web canonical sources via
docs-sync.sh --source stackbilt-web --sync-only.
- mcp.md (new sourcing) — fresh page describing the live MCP gateway
at mcp.stackbilt.dev/mcp: service-binding architecture (TAROTSCRIPT,
IMG_FORGE, ENGINE, DEPLOYER, AUTH_SERVICE), OAuth auth, transports,
and a pointer to the gateway repo for the live tool catalog.
- ecosystem.md (+4 mentions of MCP gateway) — Service Map row added,
How-They-Fit-Together diagram redrawn with the three sibling
consumers (web UI, MCP gateway, Charter CLI), Available-via list
updated.
- platform.md (+1 mention) — Access section now lists the gateway
as the third sibling consumer with explicit framing that it
shares backends with the web UI and REST API.
Note: docs-sync.sh has a frontmatter-extraction bug (greedy
'/^---$/,/^---$/p' captures markdown HR separators in the body)
that doubled api-reference.md. Repaired by hand from the upstream
canonical body + the existing local frontmatter; net diff for that
file is zero. Will file a sync-script bug as a follow-up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|**Auth**|`auth.stackbilt.dev`| Authentication service (Better Auth + D1, OAuth, SSO) — service binding from Stackbilder|
30
+
|**img-forge**|`imgforge.stackbilt.dev`|Multi-provider image generation gateway — service binding from Stackbilder|
31
+
|**MCP gateway**|`mcp.stackbilt.dev/mcp`|OAuth-authenticated MCP Worker that proxies to TarotScript / img-forge / Engine / Deployer. Sibling consumer of the platform's product workers (see [MCP Gateway](/mcp))|
For quantitative analysis of ADF's impact on autonomous system architecture, see the [Context-as-Code white paper](https://github.com/stackbilt-dev/charter-kit/blob/main/papers/context-as-code-v1.1.md).
79
100
<!-- DOCSYNC:END:charter-oss-ecosystem -->
80
101
81
-
## Stackbilder: Architecture + Scaffold
102
+
## Stackbilder: Architecture + Scaffold + Trust
103
+
104
+
The 6-mode pipeline (PRODUCT → UX → RISK → ARCHITECT → TDD → SPRINT) produces structured artifacts with cross-referenced IDs. After completion, the scaffold engine generates a deployable Cloudflare Workers project. On Pro/Team, additional capabilities run alongside the scaffold pipeline:
82
105
83
-
The 6-mode pipeline (PRODUCT → UX → RISK → ARCHITECT → TDD → SPRINT) produces structured artifacts with cross-referenced IDs. After completion, the scaffold engine generates a deployable Cloudflare Workers project.
106
+
-**Evidence Engine** — content E-E-A-T validation and tamper-evident receipts (`stackbilder.com/api/v1/evidence/*`, see [API Reference](/api-reference#evidence-engine))
-**Consultations** — CISO and CTO advisory flows backed by structured prompts and receipt-bound deliverables
109
+
-**Inline governance** — blessed-pattern enforcement, red-team review, ADR persistence (replaces the previously-standalone Compass service binding)
84
110
85
111
Available via:
86
-
-**Browser UI** at [stackbilt.dev](https://stackbilt.dev) (interactive)
87
-
-**MCP server** at `stackbilt.dev/mcp` (agent-driven, 22 tools)
88
-
-**REST API** at `stackbilt.dev/api/flow/*` (direct HTTP)
112
+
-**Browser UI** at [stackbilder.com](https://stackbilder.com) (interactive, human users)
113
+
-**REST API** at `stackbilder.com/api/*` (direct HTTP — Charter CLI, server-to-server, CI; see [API Reference](/api-reference))
114
+
-**MCP gateway** at `mcp.stackbilt.dev/mcp` (OAuth-authenticated agent access; routes scaffold/image/deploy tools to the same backend Workers — see [MCP Gateway](/mcp))
89
115
90
116
### Lightweight Agent Pattern
91
117
@@ -95,43 +121,25 @@ The recommended agent workflow downloads ~40KB total (down from 300KB+):
95
121
runFullFlowAsync → getFlowSummary polls → getArtifact per mode → getFlowScaffold
96
122
```
97
123
98
-
## Compass: Policy Brain
99
-
100
-
For current Compass routes, auth endpoints, and MCP integration surfaces, see [Compass Governance API](/compass-governance-api).
101
-
102
-
Compass is an AI governance agent with institutional memory — a ledger of ADRs, blessed patterns, and constitutional rules. It validates architecture decisions, runs red-team reviews, and drafts formal policy documents.
103
-
104
124
### Governance Modes by Plan
105
125
106
126
| Plan | Max Mode | Behavior |
107
127
|------|----------|----------|
108
128
| Free |`PASSIVE`| Log only — never blocks |
109
129
| Pro |`ADVISORY`| Warn on issues, flow continues |
110
-
|Enterprise|`ENFORCED`| Block on FAIL, require remediation |
130
+
|Team|`ENFORCED`| Block on FAIL, require remediation |
111
131
112
132
When governance mode is capped by plan tier, a soft upsell prompt appears in the `governanceState` response.
113
133
114
134
### Blessed Patterns
115
135
116
-
Compass maintains a ledger of approved technology patterns. These are injected into Stackbilder's ARCHITECT prompt automatically when governance is enabled. Example:
136
+
The platform maintains a ledger of approved technology patterns. These are injected into the ARCHITECT prompt automatically when governance is enabled. Example:
117
137
118
138
- Compute: Cloudflare Workers (not AWS Lambda)
119
139
- Database: Cloudflare D1 (not PostgreSQL)
120
140
- Cache: Cloudflare KV (not Redis)
121
141
- Queue: Cloudflare Queues (not SQS)
122
142
123
-
### CSA Transport Modes
124
-
125
-
Communication between Stackbilder and Compass supports multiple transports:
126
-
127
-
| Transport | Description |
128
-
|-----------|-------------|
129
-
|`external_http`| Public HTTPS MCP endpoint (default) |
Canary rollout percentage is configurable per-flow or via environment default.
134
-
135
143
## Worker Observability: ODD-Driven Monitoring
136
144
137
145
`@stackbilt/worker-observability` is the OSS library ([Apache-2.0](https://github.com/Stackbilt-dev/worker-observability)). The hosted Pro product on stackbilder.com wraps it with D1 storage and a dashboard.
8.**CI** — Charter blocks merges on drift violations or metric ceiling breaches
183
191
184
-
## Authentication Across Services
192
+
## Authentication
185
193
186
-
### Unified Auth (Recommended)
194
+
Stackbilder issues two credential types, both accepted at every endpoint:
187
195
188
-
One access key works at both Stackbilder and Compass:
196
+
-**Session cookie** — `better-auth.session_token`, set during OAuth sign-in (GitHub, Google) at [auth.stackbilt.dev](https://auth.stackbilt.dev). Used by the browser UI.
197
+
-**API key** — `Authorization: Bearer ea_*`, issued from `/settings`. Used by Charter CLI, server-to-server pipelines, and MCP-style consumers.
189
198
190
-
```bash
191
-
# Exchange ska_ key for a JWT
192
-
curl -X POST https://stackbilt.dev/api/auth/token \
193
-
-H "X-Access-Key: ska_..." \
194
-
-d '{"expires_in": 3600}'
195
-
# Use the returned JWT at either service
196
-
```
197
-
198
-
### Service-to-Service
199
-
200
-
For automated pipelines, each service has its own token:
0 commit comments