Turn pilot evidence into clear findings, owners, priorities, and next controlled actions.

• Stable module ownership
• Connected stage state
• Linked deterministic record references
• Webhook test plan drafted
• Protected payment path matched

ForgeLayer can demonstrate module ownership, handoffs, and human control without executing work.

The connected journey uses deterministic sample records and local state.

Confirm that the sequence and module responsibilities match the pilot team's expectations.

Use the same scenario in the Pilot, Evaluation, and Findings surfaces during reviewer sessions.

• Reviewer can explain the control journey and identify the human approval gate.

• A selected deterministic pilot scenario

No additional blocker identified for this preview finding.

• Safe Review Run summary
• Policy and verification labels
• Check and comment previews
• Webhook test plan drafted
• Protected payment path matched

The product demonstrates evidence structure, but not durable production evidence.

Verification and evidence may be simulated, derived, or preview-only.

Identify which test, build, policy, and reviewer evidence a real pilot must capture.

Define evidence sources and retention rules before expanding persistent Review Runs.

• Required evidence sources, ownership, and acceptance rules are documented.

• Workspace identity
• Evidence schema
• Retention policy

• No production persistence
• No verified evidence ingestion

• Explicit local approve, request-changes, or block decision
• Webhook test plan drafted
• Protected payment path matched

The control gate is visible, while identity, authority, and decision history remain foundation work.

Approval decisions update local preview state only.

Define who may approve each risk class and what evidence they must review.

Design workspace-scoped approval records after identity and RLS boundaries are reviewed.

• Approval roles, evidence requirements, and revocation behavior are defined.

• Production identity
• Workspace roles
• RLS

• No durable approval record
• No production approver identity

• Blocked actions
• Required control gates
• Scenario risk signals
• Webhook test plan drafted
• Protected payment path matched

RepoBrain shows how repository rules influence review, but policy authority is not established.

Deterministic policy context is not bound to a production workspace identity.

Confirm who owns repository policy and how policy changes are reviewed.

Bind repository installations and policy versions to workspace-scoped identity before writes.

• Policy ownership, versioning, and change-approval rules are documented.

• Workspace identity
• GitHub installation ownership
• Policy version records

• No production workspace boundary

• Readiness prerequisites and intentionally blocked capabilities
• Webhook test plan drafted
• Protected payment path matched

Persistent records cannot safely expand until the implemented identity, membership, role, and tenant-isolation foundation is activated and integration-tested.

The private-beta workspace is a non-persistent demo boundary.

Review the production architecture plan and approve an identity-first implementation sequence.

Implement workspace identity and tested RLS before adding durable Agent Work Records or approvals.

• Identity, membership, role, and RLS designs pass security review.

• Production architecture review

• Production auth not live
• Workspace RLS not implemented

• Disabled execution, writes, posting, merge, and persistence flags
• Webhook test plan drafted
• Protected payment path matched

The blocked posture is intentional and prevents the preview from becoming an execution path.

No repository write, GitHub posting, automatic merge, or live agent execution is available.

Keep the blocked posture until permissions, idempotency, audit events, and kill switches are reviewed.

Treat write and execution capabilities as separate, explicitly approved production phases.

• Every future side effect has an explicit gate, owner, audit event, idempotency key, and kill switch.

• Workspace identity
• Approved repository
• Audit events
• Kill switches

• No controlled execution boundary
• No production write authorization

• Deterministic activity records
• Linked evidence count
• Control outcome summaries
• Webhook test plan drafted
• Protected payment path matched

The preview demonstrates useful control questions, not measured customer behavior.

Analytics use fixed sample records and are not production telemetry.

Choose which control insights justify collecting production events.

Define event schemas, consent, retention, and privacy boundaries before enabling telemetry.

• Approved metrics have documented source events, purpose, retention, and access rules.

• Workspace identity
• Event schema
• Retention policy

• Production telemetry disabled

• Primary and supporting agent recommendations
• Capability and control-risk context
• Webhook test plan drafted
• Protected payment path matched

A future controlled intake layer could accept agent output without granting autonomous authority.

ForgeLayer recommends and plans work but does not contact or execute agents.

Validate demand and safety requirements before designing any external agent connection.

Keep external execution blocked; prototype output intake only after production foundations exist.

• A reviewed design separates task routing, output intake, verification, approval, and execution.

• Production identity
• Durable Work Records
• Verification controls

• No external agent calls
• No execution authorization