Demo journey

See how a repo moves from assessment to governed workflow.

A readiness assessment should not end with a static report. It should show where the repo stands, what happens next, and how factoryization can create a governed front door: scoped intent, evidence, checks, review, and approval attached before agentic work is trusted.

Request assessment View sample readiness report

Illustrative V1 journey using demo data. Fulfilment remains operator/agent-assisted and scope-agreed.

Assessment journey

Where the demo assessment is now, and what happens next.

Complete
Requested

Assessment requested.
Complete
Assessing

Repo context and delivery workflow evidence are being reviewed.
Current
Report ready

Readiness, blockers, risks, boundaries, and next actions are available.
Future
Plan agreed

The implementation path from readiness findings to factoryization is agreed.
Future
Front door active

Agentic work has a governed front door into the repo: intent, evidence, checks, review, and approval.
Future
Improving

Governance becomes more repeatable, enforceable, and monitored over time.

Report preview

What the report tells you.

This is a short demo-backed summary of the assessment output and implementation path.

Sample report

See what the assisted assessment produces.

This customer-zero sample report was generated from a real assisted assessment of the Software Dark Factory GTM Rails app. It shows the kind of evidence, readiness classification, gaps, boundaries, and implementation path a customer receives.

View sample readiness report

The report is generated from Bootstrap assessment evidence. GTM hosts the sample artifact; it does not claim self-serve scanning, GitHub OAuth, repo mutation, or hosted enforcement.

Readiness Assessed
Key blockers Governance path not yet installed; evidence expectations not yet standardised.
Risks AI-assisted work may reach PR review without consistent intent/evidence attached.
Boundaries No hosted enforcement or automatic repo mutation claimed.
Next actions Agree implementation path; define governed front door; add evidence expectations.

Maturity ladder

From assessed to factoryized.

Current maturity: Level 1 - Assessed. Target next maturity: Level 2 - Prepared. Longer-term goal: Level 3 - Factoryized.

The assessment puts the repo at Level 1. The next step is preparation: agreeing the implementation path. Factoryization is the point where the governed workflow and front door exist.

Level 0

Unassessed

AI-assisted work may be happening, but repo readiness is unknown.

Level 1

Assessed

Evidence-backed readiness report exists.

Level 2

Prepared

Blockers, risks, and implementation path are clear.

Level 3

Factoryized

A governed front door exists for agentic work.

Level 4

Enforced

Checks and review paths are enforced in the receiver repo.

Level 5

Monitored

Governance drift and recovery paths can be monitored.

Later levels depend on repo context, agreed implementation scope, and customer-owned enforcement decisions.

Factoryization path

From report to governed workflow.

Factoryization turns readiness findings into a governed way for agentic work to enter the repo with intent, evidence, checks, review, and approval attached.

Agree implementation path

Turn the readiness findings into a practical path toward a governed workflow.

Define governed front door

Name the controlled entry path for agentic work: scoped intent, evidence, checks, review, and customer-owned approval.

Add evidence and review expectations

Make checks, evidence, and reviewer expectations visible before trust is granted.

Activate under customer-owned controls

Run the workflow within the agreed scope and customer approval model.

This first demo shows the path. Real implementation remains assisted and scope-agreed.

Governed front door

The target state is not uncontrolled automation. It is controlled speed.

A governed front door is the repo's controlled entry path for agentic work: scoped intent, evidence, checks, review, and customer-owned approval.

scoped intent

evidence attached

checks visible

review path clear

approval remains human/customer-owned

Boundary note

Demo-backed and assisted.

This V1 journey is demo-backed and assisted. It does not yet claim self-serve repo scanning, GitHub OAuth, hosted enforcement, automatic repo mutation, or production/customer enforcement.