Agentic Engineering Governance

powered by Software Dark Factory

Controlled demo proof

Controlled demo proof

A Rails receiver is bootstrapped with the governed front door, then a real bounded change is completed through the full Software Dark Factory PR anatomy.

The demo proof page shows controlled proof of the operating model. It does not claim hosted enforcement, production/customer governance, automatic approval, automatic merge, or guaranteed correctness.

Request an assisted repo readiness assessment View the assessment journey

Controlled proof only. No hosted enforcement, production/customer governance, automatic approval, automatic merge, or guaranteed correctness is claimed.

Core proof line

Bootstrap installs. Receiver runs. Evidence proves.

Controlled proof

Homepage proof stays buyer-friendly. This page carries the technical evidence chain and boundaries.

Operating boundary

automatic_execution_permitted: false

Demo walkthrough

Watch the controlled demo walkthrough

A short Loom walkthrough shows the current controlled path from assisted assessment context to governed front door adoption and completed governed PR proof.

Open the Loom walkthrough

Some browsers block embedded Loom playback. The direct link remains the reliable demo path.

Watch on Loom

Video not loading? Watch on Loom

The recording is a walkthrough of controlled proof surfaces. The written sections below remain the claim-bounded technical evidence record.

This is a controlled proof walkthrough. It does not claim hosted enforcement, production/customer governance, automatic approval, automatic merge, billing-grade cost, or measured savings.

What the walkthrough proves

Adoption to governed work, with evidence retained.

The walkthrough proves the full path from adoption to governed work without turning the GTM site into an execution surface.

This is what governed AI-assisted delivery looks like in practice: a bounded change, a visible brief, a reviewable PR, and committed evidence for drill-down.

1

Bootstrap installs the governed front door

PR #7 adopts the receiver-local governed front door in a clean controlled Rails receiver.

2

The receiver runs local factory commands

The receiver owns the local SDF factory commands after installation. This is tooling run inside the controlled receiver, not hosted enforcement.

3

A bounded Rails change is completed

PR #8 delivers a tiny /factory-proof change through the full governed work anatomy.

4

The PR body follows the public 01-08 structure

PR #8 uses a production-style governed PR body with prompt/run log, criteria, playbooks, preflight, risk, verification, evidence, and AI usage.

5

Full evidence remains committed

The readable PR body points reviewers to committed evidence records for audit and drill-down.

Next step

Seen enough to assess your own repo?

Start with a scoped readiness assessment. We will review where your repo stands today, what evidence is missing, and what a governed front-door adoption path could look like.

Request a readiness assessment View the sample readiness report

Rails two-PR flow

PR #7 adopts the front door. PR #8 proves completed governed work.

The strongest current demo is a controlled Rails receiver flow where adoption lands before the bounded governed work slice.

main
  <- PR #7: adopt governed front door
        <- PR #8: complete governed work slice
PR #7

Purpose: adoption/factoryization proof

Shows: Bootstrap can install the governed front door

Status: draft/open controlled proof

PR #8

Purpose: completed governed work proof

Shows: a real bounded Rails change completed through the full SDF anatomy

Status: draft/open controlled proof

Governed PR anatomy

PR #8 now uses the public 01-08 governed PR shape.

The PR body is the reviewer decision surface. The committed files remain the audit trail.

This is reviewer context and evidence packaging. It is not automatic approval, automatic merge, or automatic trust judgement.

  1. 01 Prompt / Run Log recorded
  2. 02 Acceptance Criteria complete
  3. 03 Playbooks Applied complete
  4. 04 Preflight Recommendation ready
  5. 05 Risk / Confidence / Limits review_ready
  6. 06 Verification verified
  7. 07 Slice Evidence ready_for_review
  8. 08 AI Usage / Model / Cost token deltas captured; cost not billing-grade

Token economics / AI usage

Token deltas are captured evidence, not a savings claim.

The demo PR captures AI usage/economics evidence from local tool logs. Cost remains unavailable / not billing-grade, and no measured savings are claimed.

If capture is disabled or unavailable, SDF records unavailable values rather than inventing numbers.

  • Usage capture source

    reported_by_provider_through_local_tool_logs

  • Input delta

    921,936

  • Output delta

    1,213

  • Total delta

    923,149

  • Cost

    unavailable / not billing-grade

  • Measured savings

    not claimed

Completed governed work proofs

The same governed work pattern has been proven in controlled Rails and TypeScript receivers.

These are controlled receiver proofs, not a claim of all-stack coverage or native tooling for every receiver language.

Rails proof

completed_governed_work_slice_proven_in_controlled_rails_receiver

TypeScript proof

completed_governed_work_slice_proven_in_controlled_typescript_receiver

Runtime / tooling boundary

Receiver app runtime is separate from SDF factory tooling runtime.

The TypeScript receiver remains a TypeScript / Node app.
The current SDF factory tooling is Ruby-based and runs as local governance tooling, not as a production app dependency.
The TypeScript proof did not declare a Node runtime. Verification used ambient Node v24.14.0, while npm/corepack were unavailable and recorded honestly.

Governed PR output modes

Bootstrap supports multiple reviewer surfaces.

full
detailed governed evidence record
reviewer
concise reviewer-facing summary
combined
reviewer summary plus full evidence record
pr-body
production-ready PR body with key highlights and evidence pointers

Capability lifecycle

Status, drift, and recovery preview support operator review.

The controlled proof also includes receiver-local capability status, drift/status detection, recovery-plan preview, and runtime alignment guidance.

These are operator review tools, not automatic repair, automatic apply, hosted monitoring, or continuous monitoring.

receiver-local capability manifest / status
drift/status detection
recovery-plan preview
runtime alignment guidance

Proof sources

Controlled artifacts used for this proof page.

These references name the controlled proof path without adding live Bootstrap calls, GitHub API access, repo scanning, receiver mutation, hosted enforcement, or automatic PR creation.

Controlled Rails walkthrough

  • Repo: dark-factory-rails-demo-receiver
  • PR #7: Demo: adopt governed front door for full SDF walkthrough
  • PR #7 branch: demo/full-sdf-walkthrough/adopt-governed-front-door
  • PR #7 base: main
  • PR #7 status: draft/open
  • PR #8: Demo: complete governed work slice with full SDF PR anatomy
  • PR #8 branch: demo/full-sdf-walkthrough/completed-governed-work
  • PR #8 base: demo/full-sdf-walkthrough/adopt-governed-front-door
  • PR #8 status: draft/open
  • Slice: full-sdf-demo-walkthrough-proof

Claim boundary

  • automatic_execution_permitted: false
  • Controlled proof only
  • No hosted/customer enforcement
  • No automatic approval or merge
  • No billing-grade cost or measured savings

What this does not claim

Controlled proof is not customer enforcement.

This proof does not claim:

production/customer governance hosted enforcement automatic approval or merge automatic enforcement or repair automatic PR creation or approval guaranteed correctness or safety security certification or formal verification billing-grade cost or measured savings automatic optimisation or model routing optimisation arbitrary receiver coverage zero-dependency adoption native toolkit for every receiver language
Start with a scoped readiness assessment View the assessment journey