App development and staging
This is the implementation and staging reference for the Binary Networks platform. S.E.T is a module inside it. The locked product specifications remain requirements; this section records what the supplied sources actually establish.
Architecture
The Binary Networks platform has a browser app and an API. The API owns authentication, permissions, database transactions and file access. S.E.T questionnaire behavior is described in its module lifecycle.
Tenancy and data separation
MERGED, NOT DEPLOYED — a buyer is the tenant/MSSP; a client is an organization managed by that buyer. Each tenant has its own Postgres login and schema. A client's rows are scoped inside that schema, not placed in a separate database today. A85-99,317-359,654-749 A37-46
Data model
MERGED, NOT DEPLOYED — these columns come from the forward migrations in the supplied app branch. They are not an introspection of staging. Types, nullability and defaults below retain the SQL declarations. The pack identifies the deployed release, but does not introspect table columns or applied migration checksums; those are NOT VERIFIED. E13-18
S.E.T module: questionnaire lifecycle
MERGED, NOT DEPLOYED — the following is the S.E.T module's code behavior. The staging baseline predates held edits, cycles and scoped answer history; the pack explicitly identifies those wave-1 routes as not live. E13-16,59-60,69-72
Files and storage
The two upload flows are currently different. MERGED, NOT DEPLOYED — standards reserve a pending row, upload bytes, then complete the row. Answer attachments upload bytes first and insert their row afterwards; a later failure can leave an orphan. A137-154 A173-184
AI expert
APPROVED, IN BUILD — this is an approved design for the Binary Networks platform's Standards Library. It is not merged application behavior. The work file explicitly says design only; the AWS evidence says the API role has no Bedrock permission. A3-10 E28,87-88
Errors and support
MERGED, NOT DEPLOYED — the API returns a stable error code and correlation ID, not backend exception text. Fastify generates a UUID for each request. The response header x-correlation-id, error body's correlationId and log field reqId identify the same request. A26-35,153-164,189-190 A17-34
Observability and runbooks
LIVE ON STAGING — CloudWatch holds the API log group, four observed metric filters and zero nonprod CloudWatch alarms. Management has three alarms. The Grafana host and metric-read roles exist. NOT VERIFIED — which Grafana rules are loaded and successfully delivering. E68-76,93-96
Environments and deploy
MERGED, NOT DEPLOYED — local development and CI commands below are defined in the app branch. They were not executed in this documentation task.
Decisions
This register covers the supplied 2026-10-26/27 release decisions and their supporting work records. Decision approval is not deployment evidence. Initial questions and superseded answers are retained so changes in direction remain visible. Where rejection reasons are absent, this page says so rather than attributing a motive to Ron.
AWS accounts and IAM
The account list is LIVE ON STAGING as an organizational inventory. The label includes support accounts; it does not turn those accounts into staging environments. Collection scope is eu-north-1 unless the pack says otherwise. E3,7-13
AWS assets and flows
This inventory names every asset or asset group supplied by the AWS pack. It is not a complete AWS inventoryevidence-aws.md:3,12,33,47,57,66
Monitoring, Grafana and Slack
Host and provisioning
App user flows
All built flows on this page are MERGED, NOT DEPLOYED; the app pack separately identifies the older staging baseline and wave-1-only routes. Current role configuration after Ron’s fix remains NOT VERIFIED. E13-16,69-72 These are Binary Networks platform flows, including S.E.T questionnaires.
App development
MERGED, NOT DEPLOYED — commands and repository structure are verified from the supplied app branch. Latest CI success, required-check settings and actual release completion are NOT VERIFIED; a workflow definition is not a successful run.
Evidence and verification
Verified on 2026-10-27 using local reads only. No cloud commands, network commands, installs or application builds were run. All source prefixes resolve as documented on the index.