Source-backed · owner controlled
Architecture From your agent’s approved materials to site delivery and operations. Start with five stages; open one to explore its implementation.
Customer websites: In progress · deployed. Owner-reported pilot deployment; independent verification remains separate.
The system at a glance Select a stage in the map or the cards below. Only its technical diagram and source evidence will open.
Architecture overview
An architecture diagram generated by Archify.
1. Client & Local Agent · Prepared spec / approved preview · Architecture component · Explore stage
1. Client & Local Agent
Prepared spec / approved preview
Explore stage
2. Auth & Mandate Gate · Identity / ownership / permission · Architecture component · Explore stage
2. Auth & Mandate Gate
Identity / ownership / permission
Explore stage
3. Validation & Build Engine · Validation / generation / checks · Architecture component · Explore stage
3. Validation & Build Engine
Validation / generation / checks
Explore stage
4. Live Hosting & CMS · Customer sites / project landing · Architecture component · In progress · deployed
4. Live Hosting & CMS
Customer sites / project landing
In progress · deployed
5. Governance & Ops · Approval / audit / recovery · Architecture component · Explore stage
5. Governance & Ops
Approval / audit / recovery
Explore stage
Approved input
Authorized
Verified only
Audit / status
Guardrails
Legend
Backend
Cloud
Security
External
01 Client & Local Agent Prepares the site specification, assets and preview for human approval. 02 Auth & Mandate Gate Checks identity, ownership, permissions and action-specific approval. 03 Validation & Build Engine Validates approved inputs, generates catalog sites and verifies build artifacts. 04 Live Hosting & CMS Deploys verified sites and supports bounded content editing. 05 Governance & Ops Controls contributions, administration, budgets, retention and recovery.
1. Client & Local Agent Prepares the site specification, assets and preview for human approval.
Client & Local Agent
An architecture diagram generated by Archify.
Client agent · Goals and prepared materials · Architecture component · Separate local tooling
Client agent
Goals and prepared materials
Separate local tooling
Catalog preview · Pinned spec / original assets · Architecture component · Separate local tooling
Catalog preview
Pinned spec / original assets
Separate local tooling
Human approval · Approval bound to spec · Architecture component · Separate local tooling
Human approval
Approval bound to spec
Separate local tooling
Approved submission · Next: auth and mandate · Architecture component · Separate local tooling
Approved submission
Next: auth and mandate
Separate local tooling
Legacy signed request · Registered ES256 identity · Architecture component · Local emulation
Legacy signed request
Registered ES256 identity
Local emulation
Legacy signed reply · Outbox / sender / SES · Architecture component · Adapter
Legacy signed reply
Outbox / sender / SES
Adapter
Prepare
Approve
Submit
Signed result
Legend
Frontend
Backend
Security
External
Stage sources: docs/sites.md
Nodes and source evidence Client agent Implemented Local coverage: Separate local tooling
The client assistant prepares literal copy, images and the structured catalog spec. Preparation is client-side; the platform does not research or adapt images for site production.
docs/sites.md
Catalog preview Implemented Local coverage: Separate local tooling
The preview and original asset bytes are bound to the approved spec. No arbitrary styles, scripts or server-side fetching are authorized.
docs/sites.md · services/src/site/validator.ts
Human approval Implemented Local coverage: Separate local tooling
The client obtains human approval before submission. The approval declaration asserts approval; it is not a new human-signature protocol.
docs/sites.md
Approved submission Implemented Local coverage: Separate local tooling
Submission enters the authenticated platform. Selecting this boundary opens stage 2.
Explore the next stage →
apps/platform/src/app.ts
Legacy signed request Implemented Local coverage: Local emulation
The signed-email CLI and local seed create MIME requests for registered identities; platform key registration alone does not enroll an AWS email grant.
services/src/client.ts
Legacy signed reply Implemented Local coverage: Adapter
Durable outbox work is queued to the sender, signed with ES256 and sent via SES. Locally, the SES v2-to-v1 bridge captures unchanged MIME. No real inbox delivery.
services/src/sender.ts · services/src/store.ts
2. Auth & Mandate Gate Checks identity, ownership, permissions and action-specific approval.
Auth & Mandate Gate
An architecture diagram generated by Archify.
Identity and OAuth · Google / OAuth / consent · Architecture component · Separate local tooling
Identity and OAuth
Google / OAuth / consent
Separate local tooling
Platform MCP connector · Resource-bound tools · Architecture component · Separate local tooling
Platform MCP connector
Resource-bound tools
Separate local tooling
Ownership and roles · Live principal checks · Architecture component · Separate local tooling
Ownership and roles
Live principal checks
Separate local tooling
Approval and confirmation · Exact action / spec binding · Architecture component · Separate local tooling
Approval and confirmation
Exact action / spec binding
Separate local tooling
Plan and allowance · Pinned policy / atomic caps · Architecture component · Separate local tooling
Plan and allowance
Pinned policy / atomic caps
Separate local tooling
Authorized site work · Next: validation and build · Architecture component · Separate local tooling
Authorized site work
Next: validation and build
Separate local tooling
Legacy ES256 validation · Signature / scope / replay · Architecture component · Local emulation
Legacy ES256 validation
Signature / scope / replay
Local emulation
Legacy admission · Flags / task allowances · Architecture component · Local emulation
Legacy admission
Flags / task allowances
Local emulation
Scoped token
Authorize
Bind approval
Reserve
Queue
Admit
Legend
Backend
Database
Security
External
Stage sources: apps/platform/src/auth.ts
Nodes and source evidence Identity and OAuth Implemented Local coverage: Separate local tooling
Better Auth manages login and OAuth consent. Consent grants a scoped connector mandate; it does not approve a particular site or deployment.
apps/platform/src/auth.ts
Platform MCP connector Implemented Local coverage: Separate local tooling
The implemented MCP connector authenticates resource-bound calls and exposes role-scoped tools. It is separate from future customer MCP products.
apps/platform/src/app.ts · apps/platform/src/tools.ts
Ownership and roles Implemented Local coverage: Separate local tooling
Ownership and live role permissions are rechecked before state changes and provider actions. Accounts cannot use normal site tools to access another owner’s site.
apps/platform/src/tools.ts · apps/platform/src/sites.ts
Approval and confirmation Implemented Local coverage: Separate local tooling
Build/deploy gates bind the spec and require exact confirmation strings. An OAuth grant or agent statement does not replace action approval.
apps/platform/src/sites.ts · apps/platform/src/sites.ts
Plan and allowance Implemented Local coverage: Separate local tooling
Versioned policies and atomic reservations enforce bounded changes. CMS content edits do not consume site-change allowance; unknown deployments retain reservations.
apps/platform/src/sites.ts · services/src/site/validator.ts
Authorized site work Implemented Local coverage: Separate local tooling
Authorized site work enters the durable build queue. Selecting this boundary opens stage 3.
Explore the next stage →
apps/platform/src/sites.ts
Legacy ES256 validation Implemented Local coverage: Local emulation
Signed email validates the registered grant, signature, expiry, destination and replay before durable admission. This is independent of platform OAuth.
services/src/intake.ts · services/src/protocol.ts
Legacy admission Implemented Local coverage: Local emulation
Email admission applies operating flags and per-partner/day limits; runtime reserves $1 per task against $10 monthly model allowance, with two global concurrent tasks.
services/src/intake.ts · contracts/limits.defaults.json
3. Validation & Build Engine Validates approved inputs, generates catalog sites and verifies build artifacts.
Validation & Build Engine
An architecture diagram generated by Archify.
Spec and asset validation · Pinned policy / byte hashes · Architecture component · Separate local tooling
Spec and asset validation
Pinned policy / byte hashes
Separate local tooling
Durable Postgres jobs · Owned queue / audit state · Architecture component · Separate local tooling
Durable Postgres jobs
Owned queue / audit state
Separate local tooling
Astro catalog generator · Fixed blocks / design tokens · Architecture component · Separate local tooling
Astro catalog generator
Fixed blocks / design tokens
Separate local tooling
Agents verification · Build / a11y / visual checks · Architecture component · Separate local tooling
Agents verification
Build / a11y / visual checks
Separate local tooling
Verified artifact store · Private reports / output hashes · Architecture component · Separate local tooling
Verified artifact store
Private reports / output hashes
Separate local tooling
Verified deployment gate · Next: hosting and CMS · Architecture component · Cloud-only
Verified deployment gate
Next: hosting and CMS
Cloud-only
Legacy SES intake · S3 / SNS / SQS / Lambda · Architecture component · Adapter
Legacy SES intake
S3 / SNS / SQS / Lambda
Adapter
Legacy durable dispatch · DynamoDB / Streams / SQS · Architecture component · Local emulation
Legacy durable dispatch
DynamoDB / Streams / SQS
Local emulation
Legacy brief executor · OpenAI analysis / cleanup · Architecture component · Mock
Legacy brief executor
OpenAI analysis / cleanup
Mock
Legacy input / result S3 · 30 days / pending 7 days · Architecture component · Local emulation
Legacy input / result S3
30 days / pending 7 days
Local emulation
Queue
Generate
Verify
Checked output
Deploy gate
Commit
SQS trigger
Save result
Legend
Backend
Database
Security
Message bus
External
Stage sources: apps/platform/src/sites.ts · packages/generator/src/render.ts
Nodes and source evidence Spec and asset validation Implemented Local coverage: Separate local tooling
Validates structured site specs, original raster bytes and approval/preview digests. No OCR, research, image editing or free-text interpretation is part of catalog generation.
apps/platform/src/sites.ts · packages/generator/src/render.ts
Durable Postgres jobs Implemented Local coverage: Separate local tooling
Persistent jobs and transactional audit/accounting survive interruptions. A worker claims queued jobs; uncertain provider outcomes require reconciliation rather than blind replay.
apps/platform/src/sites.ts · apps/platform/migrations/004-sites.sql
Astro catalog generator Implemented Local coverage: Separate local tooling
Deterministic rendering uses the fixed catalog and approved tokens. Prepared assets are copied byte-identically; source and output hashes bind the artifacts.
packages/generator/src/render.ts
Agents verification Implemented Local coverage: Separate local tooling
A secret-free hosted Agents sandbox runs the fixed build, accessibility, link and approved-preview checks. Local checks are separate from independent hosted-cloud evidence.
packages/generator/src/verification.ts · packages/generator/src/verification.ts
Verified artifact store Implemented Local coverage: Separate local tooling
The controller stores verified output, reports and screenshots as private artifacts. Model text alone cannot authorize deployment.
apps/platform/src/sites.ts · packages/generator/src/storage.ts
Verified deployment gate Implemented Local coverage: Cloud-only
Only verified bytes and a newly checked mandate reach the provider adapter. Selecting this boundary opens stage 4.
Explore the next stage →
apps/platform/src/sites.ts
Legacy SES intake Implemented Local coverage: Adapter
The signed-email foundation follows SES receipt storage and SNS/SQS into intake. The local receipt-rule adapter executes the synthesized S3/SNS actions; it does not receive internet SMTP.
infra/src/email.ts · services/src/intake.ts
Legacy durable dispatch Implemented Local coverage: Local emulation
Durable task/outbox state and DynamoDB Streams enqueue work. Tasks/outbox retain 30 days; replay/audit retain 90 days; DLQs retain 14 days. Expiration is asynchronous.
services/src/intake.ts · services/src/dispatcher.ts
Legacy brief executor Implemented Local coverage: Mock
Production workers analyze a brief, store results, delete provider sessions and release concurrency. The local OpenAI stand-in returns a fixed fictional fixture; this is not the catalog build engine.
services/src/runtime.ts
Legacy input / result S3 Implemented Local coverage: Local emulation
Authenticated inputs and results remain private. Accepted content retains 30 days and abandoned pending inputs seven days; lifecycle deletion is asynchronous.
services/src/store.ts · infra/src/email.ts
4. Live Hosting & CMS Deploys verified sites and supports bounded content editing.
Customer websites: In progress · deployed. Deployment reported by Carlos Olivera Terrazas; independent hosted end-to-end verification remains separate.
Live Hosting & CMS
An architecture diagram generated by Archify.
Customer websites · In progress / deployed · Architecture component · Cloud-only
Customer websites
In progress / deployed
Cloud-only
Isolated Railway project · Protected targets / resource caps · Architecture component · Cloud-only
Isolated Railway project
Protected targets / resource caps
Cloud-only
Caddy site delivery · Verified static artifacts · Architecture component · Separate local tooling
Caddy site delivery
Verified static artifacts
Separate local tooling
PocketBase CMS · Private service / published reads · Architecture component · Separate local tooling
PocketBase CMS
Private service / published reads
Separate local tooling
Client content editor · Content edits without redeploy · Architecture component · Separate local tooling
Client content editor
Content edits without redeploy
Separate local tooling
Domain / TLS status · Provider readiness / owner DNS · Architecture component · Cloud-only
Domain / TLS status
Provider readiness / owner DNS
Cloud-only
Project landing S3 · Private normal website build · Architecture component · Local emulation
Project landing S3
Private normal website build
Local emulation
Project CloudFront · TLS / origin access / CSP · Architecture component · Cloud-only
Project CloudFront
TLS / origin access / CSP
Cloud-only
Guarded target
Deploy
Private proxy
Editor access
Readiness
Private origin
Legend
Frontend
Backend
Database
Cloud
Stage sources: docs/release-verification.md · apps/platform/src/sites.ts
Nodes and source evidence Customer websites In progress · deployed Local coverage: Cloud-only
Carlos Olivera Terrazas reports the customer-site build/hosting pilot deployed and still in progress. This task has not independently inspected a hosted end-to-end transcript or customer site. Earlier local verification and independent cloud gates remain separate.
docs/release-verification.md · apps/platform/src/sites.ts
Isolated Railway project Implemented Local coverage: Cloud-only
The provider adapter isolates each client project/environment, protects shared projects and checks resource identity/caps. Owner-reported deployment does not independently verify every provider control.
packages/generator/src/deploy.ts
Caddy site delivery Implemented Local coverage: Separate local tooling
Caddy serves verified static artifacts and only approved CMS proxy routes. Customer hosting is distinct from the AWS project landing.
packages/generator/src/deploy.ts · packages/generator/src/deploy.ts
PocketBase CMS Implemented Local coverage: Separate local tooling
Only bound catalog/blog/announcement collections exist. Anonymous reads expose published content; editor writes are authenticated. CMS data persists across bounded site revisions.
packages/generator/src/pocketbase.ts
Client content editor Implemented Local coverage: Separate local tooling
Content edits use the authenticated CMS editor and do not consume site-change allowance. Client account creation and privileged CMS settings are blocked.
packages/generator/src/pocketbase.ts
Domain / TLS status Implemented Local coverage: Cloud-only
The adapter observes deployment/domain/certificate state; DNS is not changed by the site tool. Live provider readiness remains an independent verification question.
packages/generator/src/deploy.ts
Project landing S3 Implemented Local coverage: Local emulation
The project landing and release snapshots use private S3. The existing LocalStack quickstart serves this normal website build; it does not deploy customer Railway sites.
infra/src/app.ts
Project CloudFront Implemented Local coverage: Cloud-only
CloudFront delivers the project landing with origin access control, cache and security headers. Public TLS/DNS and cloud caching are outside LocalStack.
infra/src/app.ts
5. Governance & Ops Controls contributions, administration, budgets, retention and recovery.
Governance & Ops
An architecture diagram generated by Archify.
Agent contribution · Authorized repository work · Architecture component · Cloud-only
Agent contribution
Authorized repository work
Cloud-only
Operator broker · Fixed App token profiles · Architecture component · Mock
Operator broker
Fixed App token profiles
Mock
PR and required checks · Read-only CI / trusted policy · Architecture component · Cloud-only
PR and required checks
Read-only CI / trusted policy
Cloud-only
Owner approval · Carlos / exact current head · Architecture component · Cloud-only
Owner approval
Carlos / exact current head
Cloud-only
Approved merge / main CI · Main-only delivery authority · Architecture component · Cloud-only
Approved merge / main CI
Main-only delivery authority
Cloud-only
Website release · Verify / snapshot restoration · Architecture component · Cloud-only
Website release
Verify / snapshot restoration
Cloud-only
EventBridge reconciliation · Retries / provider cleanup · Architecture component · Local emulation
EventBridge reconciliation
Retries / provider cleanup
Local emulation
Budgets / alarms / retention · $1 task / $10 model / $15 AWS · Architecture component · Local emulation
Budgets / alarms / retention
$1 task / $10 model / $15 AWS
Local emulation
Testers and chat superadmin · Audited / staging-only reset · Architecture component · Separate local tooling
Testers and chat superadmin
Audited / staging-only reset
Separate local tooling
Postgres audit / recovery · Atomic results / unknown outcomes · Architecture component · Separate local tooling
Postgres audit / recovery
Atomic results / unknown outcomes
Separate local tooling
Isolated human support · 7-day content / 30-day logs · Architecture component · Local emulation
Isolated human support
7-day content / 30-day logs
Local emulation
Future customer products · Payments / apps / MCP / plugins · Architecture component · Planned
Future customer products
Payments / apps / MCP / plugins
Planned
Authorized
App token
Review
Approve head
Main push
Observe
Audit result
Legend
Backend
Database
Cloud
Security
External
Stage sources: AGENTS.md
Nodes and source evidence Agent contribution Implemented Local coverage: Cloud-only
Repository engineering is a governed contribution workflow, not autonomous work performed by the legacy brief-analysis service.
AGENTS.md
Operator broker Implemented Local coverage: Mock
The enabled development broker issues fixed repository-scoped App tokens. Locally it mints against fake GitHub; PR requests are recorded without real publication.
services/src/operator.ts
PR and required checks Implemented Local coverage: Cloud-only
PR checks and the external App-bound policy evaluate sensitive paths and current-head approval. The advisory local integration workflow remains blocked from App publication by missing workflow-write permission.
services/src/operator.ts · .github/workflows/release.yml
Owner approval Implemented Local coverage: Cloud-only
Only Carlos Olivera Terrazas can approve the current sensitive-path head. Automation cannot manufacture approval; repository auto-merge remains disabled.
services/src/policy.ts · AGENTS.md
Approved merge / main CI Implemented Local coverage: Cloud-only
An approved merge permits main CI website delivery. PR jobs cannot deploy; infrastructure activation remains separately owner controlled.
.github/workflows/release.yml · AGENTS.md
Website release Implemented Local coverage: Cloud-only
Website delivery uploads the normal build, checks MIME/checksums/cache and restores a release snapshot after failed verification. Preparing this page is not live publication.
services/scripts/deploy-website.mjs · services/scripts/website-content-type.mjs
EventBridge reconciliation Implemented Local coverage: Local emulation
The one-minute watchdog reconciles runtime, cleanup and outbox work and observes committed model dollars. Real scheduled Lambda activity is tested locally.
services/src/watchdog.ts · infra/src/runtime.ts
Budgets / alarms / retention Implemented Local coverage: Local emulation
Application allowance is $1/task and $10/month; the model warning is $8. Failures/DLQ depth alarm at one; AWS $15 notification thresholds are 50/80/100 percent. Storage/state/log retention is 7/30/90 days with 14-day DLQs. TTL/lifecycle expiry is asynchronous. Billing budgets and owner notifications are cloud-only and are not hard spending caps.
infra/src/controls.ts · infra/src/email.ts · infra/src/runtime.ts
Testers and chat superadmin Implemented Local coverage: Separate local tooling
Tester jobs remain test-only in staging. Superadmin tools audit administration and guarded reset; no private credentials or cross-client authority enter the architecture page.
apps/platform/src/store.ts · apps/platform/src/sites.ts
Postgres audit / recovery Implemented Local coverage: Separate local tooling
Administrative results and site actions persist in audit transactions. Interrupted/unknown deployments retain reservations and require explicit reconciliation.
apps/platform/src/sites.ts · apps/platform/src/store.ts
Isolated human support Implemented Local coverage: Local emulation
Separate support storage/ledger/queue/worker handles human messages; SES feedback updates delivery/suppression. Support content/ledger retains seven days, logs 30 days and DLQs 14 days. The signed-agent fixture does not establish support inbox delivery.
services/src/support.ts · services/src/feedback.ts
Future customer products Planned Local coverage: Planned
Payments/checkout and future customer apps, MCP products and plugins remain planned. This excludes the implemented platform MCP connector and the in-progress deployed website pilot.
docs/vision.md
Explore a stage Client & Local Agent 1. Client & Local Agent Prepares the site specification, assets and preview for human approval.
Client & Local Agent
An architecture diagram generated by Archify.
Client agent · Goals and prepared materials · Architecture component · Separate local tooling
Client agent
Goals and prepared materials
Separate local tooling
Catalog preview · Pinned spec / original assets · Architecture component · Separate local tooling
Catalog preview
Pinned spec / original assets
Separate local tooling
Human approval · Approval bound to spec · Architecture component · Separate local tooling
Human approval
Approval bound to spec
Separate local tooling
Approved submission · Next: auth and mandate · Architecture component · Separate local tooling
Approved submission
Next: auth and mandate
Separate local tooling
Legacy signed request · Registered ES256 identity · Architecture component · Local emulation
Legacy signed request
Registered ES256 identity
Local emulation
Legacy signed reply · Outbox / sender / SES · Architecture component · Adapter
Legacy signed reply
Outbox / sender / SES
Adapter
Prepare
Approve
Submit
Signed result
Legend
Frontend
Backend
Security
External
Stage sources: docs/sites.md
Nodes and source evidence Client agent Implemented Local coverage: Separate local tooling
The client assistant prepares literal copy, images and the structured catalog spec. Preparation is client-side; the platform does not research or adapt images for site production.
docs/sites.md
Catalog preview Implemented Local coverage: Separate local tooling
The preview and original asset bytes are bound to the approved spec. No arbitrary styles, scripts or server-side fetching are authorized.
docs/sites.md · services/src/site/validator.ts
Human approval Implemented Local coverage: Separate local tooling
The client obtains human approval before submission. The approval declaration asserts approval; it is not a new human-signature protocol.
docs/sites.md
Approved submission Implemented Local coverage: Separate local tooling
Submission enters the authenticated platform. Selecting this boundary opens stage 2.
Explore the next stage →
apps/platform/src/app.ts
Legacy signed request Implemented Local coverage: Local emulation
The signed-email CLI and local seed create MIME requests for registered identities; platform key registration alone does not enroll an AWS email grant.
services/src/client.ts
Legacy signed reply Implemented Local coverage: Adapter
Durable outbox work is queued to the sender, signed with ES256 and sent via SES. Locally, the SES v2-to-v1 bridge captures unchanged MIME. No real inbox delivery.
services/src/sender.ts · services/src/store.ts
Auth & Mandate Gate 2. Auth & Mandate Gate Checks identity, ownership, permissions and action-specific approval.
Auth & Mandate Gate
An architecture diagram generated by Archify.
Identity and OAuth · Google / OAuth / consent · Architecture component · Separate local tooling
Identity and OAuth
Google / OAuth / consent
Separate local tooling
Platform MCP connector · Resource-bound tools · Architecture component · Separate local tooling
Platform MCP connector
Resource-bound tools
Separate local tooling
Ownership and roles · Live principal checks · Architecture component · Separate local tooling
Ownership and roles
Live principal checks
Separate local tooling
Approval and confirmation · Exact action / spec binding · Architecture component · Separate local tooling
Approval and confirmation
Exact action / spec binding
Separate local tooling
Plan and allowance · Pinned policy / atomic caps · Architecture component · Separate local tooling
Plan and allowance
Pinned policy / atomic caps
Separate local tooling
Authorized site work · Next: validation and build · Architecture component · Separate local tooling
Authorized site work
Next: validation and build
Separate local tooling
Legacy ES256 validation · Signature / scope / replay · Architecture component · Local emulation
Legacy ES256 validation
Signature / scope / replay
Local emulation
Legacy admission · Flags / task allowances · Architecture component · Local emulation
Legacy admission
Flags / task allowances
Local emulation
Scoped token
Authorize
Bind approval
Reserve
Queue
Admit
Legend
Backend
Database
Security
External
Stage sources: apps/platform/src/auth.ts
Nodes and source evidence Identity and OAuth Implemented Local coverage: Separate local tooling
Better Auth manages login and OAuth consent. Consent grants a scoped connector mandate; it does not approve a particular site or deployment.
apps/platform/src/auth.ts
Platform MCP connector Implemented Local coverage: Separate local tooling
The implemented MCP connector authenticates resource-bound calls and exposes role-scoped tools. It is separate from future customer MCP products.
apps/platform/src/app.ts · apps/platform/src/tools.ts
Ownership and roles Implemented Local coverage: Separate local tooling
Ownership and live role permissions are rechecked before state changes and provider actions. Accounts cannot use normal site tools to access another owner’s site.
apps/platform/src/tools.ts · apps/platform/src/sites.ts
Approval and confirmation Implemented Local coverage: Separate local tooling
Build/deploy gates bind the spec and require exact confirmation strings. An OAuth grant or agent statement does not replace action approval.
apps/platform/src/sites.ts · apps/platform/src/sites.ts
Plan and allowance Implemented Local coverage: Separate local tooling
Versioned policies and atomic reservations enforce bounded changes. CMS content edits do not consume site-change allowance; unknown deployments retain reservations.
apps/platform/src/sites.ts · services/src/site/validator.ts
Authorized site work Implemented Local coverage: Separate local tooling
Authorized site work enters the durable build queue. Selecting this boundary opens stage 3.
Explore the next stage →
apps/platform/src/sites.ts
Legacy ES256 validation Implemented Local coverage: Local emulation
Signed email validates the registered grant, signature, expiry, destination and replay before durable admission. This is independent of platform OAuth.
services/src/intake.ts · services/src/protocol.ts
Legacy admission Implemented Local coverage: Local emulation
Email admission applies operating flags and per-partner/day limits; runtime reserves $1 per task against $10 monthly model allowance, with two global concurrent tasks.
services/src/intake.ts · contracts/limits.defaults.json
Validation & Build Engine 3. Validation & Build Engine Validates approved inputs, generates catalog sites and verifies build artifacts.
Validation & Build Engine
An architecture diagram generated by Archify.
Spec and asset validation · Pinned policy / byte hashes · Architecture component · Separate local tooling
Spec and asset validation
Pinned policy / byte hashes
Separate local tooling
Durable Postgres jobs · Owned queue / audit state · Architecture component · Separate local tooling
Durable Postgres jobs
Owned queue / audit state
Separate local tooling
Astro catalog generator · Fixed blocks / design tokens · Architecture component · Separate local tooling
Astro catalog generator
Fixed blocks / design tokens
Separate local tooling
Agents verification · Build / a11y / visual checks · Architecture component · Separate local tooling
Agents verification
Build / a11y / visual checks
Separate local tooling
Verified artifact store · Private reports / output hashes · Architecture component · Separate local tooling
Verified artifact store
Private reports / output hashes
Separate local tooling
Verified deployment gate · Next: hosting and CMS · Architecture component · Cloud-only
Verified deployment gate
Next: hosting and CMS
Cloud-only
Legacy SES intake · S3 / SNS / SQS / Lambda · Architecture component · Adapter
Legacy SES intake
S3 / SNS / SQS / Lambda
Adapter
Legacy durable dispatch · DynamoDB / Streams / SQS · Architecture component · Local emulation
Legacy durable dispatch
DynamoDB / Streams / SQS
Local emulation
Legacy brief executor · OpenAI analysis / cleanup · Architecture component · Mock
Legacy brief executor
OpenAI analysis / cleanup
Mock
Legacy input / result S3 · 30 days / pending 7 days · Architecture component · Local emulation
Legacy input / result S3
30 days / pending 7 days
Local emulation
Queue
Generate
Verify
Checked output
Deploy gate
Commit
SQS trigger
Save result
Legend
Backend
Database
Security
Message bus
External
Stage sources: apps/platform/src/sites.ts · packages/generator/src/render.ts
Nodes and source evidence Spec and asset validation Implemented Local coverage: Separate local tooling
Validates structured site specs, original raster bytes and approval/preview digests. No OCR, research, image editing or free-text interpretation is part of catalog generation.
apps/platform/src/sites.ts · packages/generator/src/render.ts
Durable Postgres jobs Implemented Local coverage: Separate local tooling
Persistent jobs and transactional audit/accounting survive interruptions. A worker claims queued jobs; uncertain provider outcomes require reconciliation rather than blind replay.
apps/platform/src/sites.ts · apps/platform/migrations/004-sites.sql
Astro catalog generator Implemented Local coverage: Separate local tooling
Deterministic rendering uses the fixed catalog and approved tokens. Prepared assets are copied byte-identically; source and output hashes bind the artifacts.
packages/generator/src/render.ts
Agents verification Implemented Local coverage: Separate local tooling
A secret-free hosted Agents sandbox runs the fixed build, accessibility, link and approved-preview checks. Local checks are separate from independent hosted-cloud evidence.
packages/generator/src/verification.ts · packages/generator/src/verification.ts
Verified artifact store Implemented Local coverage: Separate local tooling
The controller stores verified output, reports and screenshots as private artifacts. Model text alone cannot authorize deployment.
apps/platform/src/sites.ts · packages/generator/src/storage.ts
Verified deployment gate Implemented Local coverage: Cloud-only
Only verified bytes and a newly checked mandate reach the provider adapter. Selecting this boundary opens stage 4.
Explore the next stage →
apps/platform/src/sites.ts
Legacy SES intake Implemented Local coverage: Adapter
The signed-email foundation follows SES receipt storage and SNS/SQS into intake. The local receipt-rule adapter executes the synthesized S3/SNS actions; it does not receive internet SMTP.
infra/src/email.ts · services/src/intake.ts
Legacy durable dispatch Implemented Local coverage: Local emulation
Durable task/outbox state and DynamoDB Streams enqueue work. Tasks/outbox retain 30 days; replay/audit retain 90 days; DLQs retain 14 days. Expiration is asynchronous.
services/src/intake.ts · services/src/dispatcher.ts
Legacy brief executor Implemented Local coverage: Mock
Production workers analyze a brief, store results, delete provider sessions and release concurrency. The local OpenAI stand-in returns a fixed fictional fixture; this is not the catalog build engine.
services/src/runtime.ts
Legacy input / result S3 Implemented Local coverage: Local emulation
Authenticated inputs and results remain private. Accepted content retains 30 days and abandoned pending inputs seven days; lifecycle deletion is asynchronous.
services/src/store.ts · infra/src/email.ts
Live Hosting & CMS 4. Live Hosting & CMS Deploys verified sites and supports bounded content editing.
Customer websites: In progress · deployed. Deployment reported by Carlos Olivera Terrazas; independent hosted end-to-end verification remains separate.
Live Hosting & CMS
An architecture diagram generated by Archify.
Customer websites · In progress / deployed · Architecture component · Cloud-only
Customer websites
In progress / deployed
Cloud-only
Isolated Railway project · Protected targets / resource caps · Architecture component · Cloud-only
Isolated Railway project
Protected targets / resource caps
Cloud-only
Caddy site delivery · Verified static artifacts · Architecture component · Separate local tooling
Caddy site delivery
Verified static artifacts
Separate local tooling
PocketBase CMS · Private service / published reads · Architecture component · Separate local tooling
PocketBase CMS
Private service / published reads
Separate local tooling
Client content editor · Content edits without redeploy · Architecture component · Separate local tooling
Client content editor
Content edits without redeploy
Separate local tooling
Domain / TLS status · Provider readiness / owner DNS · Architecture component · Cloud-only
Domain / TLS status
Provider readiness / owner DNS
Cloud-only
Project landing S3 · Private normal website build · Architecture component · Local emulation
Project landing S3
Private normal website build
Local emulation
Project CloudFront · TLS / origin access / CSP · Architecture component · Cloud-only
Project CloudFront
TLS / origin access / CSP
Cloud-only
Guarded target
Deploy
Private proxy
Editor access
Readiness
Private origin
Legend
Frontend
Backend
Database
Cloud
Stage sources: docs/release-verification.md · apps/platform/src/sites.ts
Nodes and source evidence Customer websites In progress · deployed Local coverage: Cloud-only
Carlos Olivera Terrazas reports the customer-site build/hosting pilot deployed and still in progress. This task has not independently inspected a hosted end-to-end transcript or customer site. Earlier local verification and independent cloud gates remain separate.
docs/release-verification.md · apps/platform/src/sites.ts
Isolated Railway project Implemented Local coverage: Cloud-only
The provider adapter isolates each client project/environment, protects shared projects and checks resource identity/caps. Owner-reported deployment does not independently verify every provider control.
packages/generator/src/deploy.ts
Caddy site delivery Implemented Local coverage: Separate local tooling
Caddy serves verified static artifacts and only approved CMS proxy routes. Customer hosting is distinct from the AWS project landing.
packages/generator/src/deploy.ts · packages/generator/src/deploy.ts
PocketBase CMS Implemented Local coverage: Separate local tooling
Only bound catalog/blog/announcement collections exist. Anonymous reads expose published content; editor writes are authenticated. CMS data persists across bounded site revisions.
packages/generator/src/pocketbase.ts
Client content editor Implemented Local coverage: Separate local tooling
Content edits use the authenticated CMS editor and do not consume site-change allowance. Client account creation and privileged CMS settings are blocked.
packages/generator/src/pocketbase.ts
Domain / TLS status Implemented Local coverage: Cloud-only
The adapter observes deployment/domain/certificate state; DNS is not changed by the site tool. Live provider readiness remains an independent verification question.
packages/generator/src/deploy.ts
Project landing S3 Implemented Local coverage: Local emulation
The project landing and release snapshots use private S3. The existing LocalStack quickstart serves this normal website build; it does not deploy customer Railway sites.
infra/src/app.ts
Project CloudFront Implemented Local coverage: Cloud-only
CloudFront delivers the project landing with origin access control, cache and security headers. Public TLS/DNS and cloud caching are outside LocalStack.
infra/src/app.ts
Governance & Ops 5. Governance & Ops Controls contributions, administration, budgets, retention and recovery.
Governance & Ops
An architecture diagram generated by Archify.
Agent contribution · Authorized repository work · Architecture component · Cloud-only
Agent contribution
Authorized repository work
Cloud-only
Operator broker · Fixed App token profiles · Architecture component · Mock
Operator broker
Fixed App token profiles
Mock
PR and required checks · Read-only CI / trusted policy · Architecture component · Cloud-only
PR and required checks
Read-only CI / trusted policy
Cloud-only
Owner approval · Carlos / exact current head · Architecture component · Cloud-only
Owner approval
Carlos / exact current head
Cloud-only
Approved merge / main CI · Main-only delivery authority · Architecture component · Cloud-only
Approved merge / main CI
Main-only delivery authority
Cloud-only
Website release · Verify / snapshot restoration · Architecture component · Cloud-only
Website release
Verify / snapshot restoration
Cloud-only
EventBridge reconciliation · Retries / provider cleanup · Architecture component · Local emulation
EventBridge reconciliation
Retries / provider cleanup
Local emulation
Budgets / alarms / retention · $1 task / $10 model / $15 AWS · Architecture component · Local emulation
Budgets / alarms / retention
$1 task / $10 model / $15 AWS
Local emulation
Testers and chat superadmin · Audited / staging-only reset · Architecture component · Separate local tooling
Testers and chat superadmin
Audited / staging-only reset
Separate local tooling
Postgres audit / recovery · Atomic results / unknown outcomes · Architecture component · Separate local tooling
Postgres audit / recovery
Atomic results / unknown outcomes
Separate local tooling
Isolated human support · 7-day content / 30-day logs · Architecture component · Local emulation
Isolated human support
7-day content / 30-day logs
Local emulation
Future customer products · Payments / apps / MCP / plugins · Architecture component · Planned
Future customer products
Payments / apps / MCP / plugins
Planned
Authorized
App token
Review
Approve head
Main push
Observe
Audit result
Legend
Backend
Database
Cloud
Security
External
Stage sources: AGENTS.md
Nodes and source evidence Agent contribution Implemented Local coverage: Cloud-only
Repository engineering is a governed contribution workflow, not autonomous work performed by the legacy brief-analysis service.
AGENTS.md
Operator broker Implemented Local coverage: Mock
The enabled development broker issues fixed repository-scoped App tokens. Locally it mints against fake GitHub; PR requests are recorded without real publication.
services/src/operator.ts
PR and required checks Implemented Local coverage: Cloud-only
PR checks and the external App-bound policy evaluate sensitive paths and current-head approval. The advisory local integration workflow remains blocked from App publication by missing workflow-write permission.
services/src/operator.ts · .github/workflows/release.yml
Owner approval Implemented Local coverage: Cloud-only
Only Carlos Olivera Terrazas can approve the current sensitive-path head. Automation cannot manufacture approval; repository auto-merge remains disabled.
services/src/policy.ts · AGENTS.md
Approved merge / main CI Implemented Local coverage: Cloud-only
An approved merge permits main CI website delivery. PR jobs cannot deploy; infrastructure activation remains separately owner controlled.
.github/workflows/release.yml · AGENTS.md
Website release Implemented Local coverage: Cloud-only
Website delivery uploads the normal build, checks MIME/checksums/cache and restores a release snapshot after failed verification. Preparing this page is not live publication.
services/scripts/deploy-website.mjs · services/scripts/website-content-type.mjs
EventBridge reconciliation Implemented Local coverage: Local emulation
The one-minute watchdog reconciles runtime, cleanup and outbox work and observes committed model dollars. Real scheduled Lambda activity is tested locally.
services/src/watchdog.ts · infra/src/runtime.ts
Budgets / alarms / retention Implemented Local coverage: Local emulation
Application allowance is $1/task and $10/month; the model warning is $8. Failures/DLQ depth alarm at one; AWS $15 notification thresholds are 50/80/100 percent. Storage/state/log retention is 7/30/90 days with 14-day DLQs. TTL/lifecycle expiry is asynchronous. Billing budgets and owner notifications are cloud-only and are not hard spending caps.
infra/src/controls.ts · infra/src/email.ts · infra/src/runtime.ts
Testers and chat superadmin Implemented Local coverage: Separate local tooling
Tester jobs remain test-only in staging. Superadmin tools audit administration and guarded reset; no private credentials or cross-client authority enter the architecture page.
apps/platform/src/store.ts · apps/platform/src/sites.ts
Postgres audit / recovery Implemented Local coverage: Separate local tooling
Administrative results and site actions persist in audit transactions. Interrupted/unknown deployments retain reservations and require explicit reconciliation.
apps/platform/src/sites.ts · apps/platform/src/store.ts
Isolated human support Implemented Local coverage: Local emulation
Separate support storage/ledger/queue/worker handles human messages; SES feedback updates delivery/suppression. Support content/ledger retains seven days, logs 30 days and DLQs 14 days. The signed-agent fixture does not establish support inbox delivery.
services/src/support.ts · services/src/feedback.ts
Future customer products Planned Local coverage: Planned
Payments/checkout and future customer apps, MCP products and plugins remain planned. This excludes the implemented platform MCP connector and the in-progress deployed website pilot.
docs/vision.md
Run the same foundation locally With Docker and Node.js 22, run npm --prefix infra run local:quickstart. The LocalStack environment runs the AWS signed-email foundation and serves the normal project website build.
The auth/MCP platform, Astro generator and PocketBase/Caddy have separate local tooling ; they are not started by this LocalStack quickstart. See platform setup and site/CMS checks .
Local emulation — shared AWS resources/workersMock — fixed external-service responsesAdapter — explicit protocol boundarySeparate local tooling — not in this quickstartCloud-only — skipped by this local setupPlanned — future customer productsCloudFront, public DNS/TLS, production OIDC, provider hosting, AWS billing budgets, real mailbox delivery and owner notifications are cloud-only here. A local pass does not establish production delivery or IAM enforcement. TTL/lifecycle expiration is asynchronous; billing notifications are not hard spending caps.
Quickstart, cleanup, coverage and troubleshooting →
Generated with Archify 3.0.1 (MIT ). Pinned source b37f8419 ; node links target main. Release evidence . This page is prepared for review and release.
