Back to registry
↻ Workflow OS ✓ Validated Updated Not dated

Buildprint Mapper OS

Use Mapper OS when you already have a working repo and want an agent to turn it into a clean, reusable Buildprint: map the source, choose a scoped candidate, then extract a selected-buildprint packet that a fresh agent can implement through product-led phase-flow, proof gates, and honest runtime evidence without reading the original code.

Package JSON
What this builds

A reusable agent workflow packet.

A repo-to-Buildprint workflow that preserves scope fidelity, generates product-led executable phase files, enforces runtime evidence honesty, embeds visual/product direction from a maintained vision guide, and proves the packet with fresh-agent replay instead of trusting a static spec.

  • Repo mapping prompt for Codex, Cursor, Claude Code, or another coding agent
  • SYSTEM_MAP.md with architecture, flows, data, integrations, tests, side effects, and unknowns
  • BUILDPRINT_CANDIDATES.md with scoped reusable Buildprint options
  • A selected-buildprint/ executable packet with BUILDPRINT.md, 01-questions.md, 02-project-setup.md, blueprint.yaml, phase-index.yaml, phase-flow.md, phase files, 04-evaluation.md, and evidence schema
  • Phase-flow execution contract requiring .buildprint/phase-runs/<phase-id>/plan.md, proof.md, and evidence rows
  • Runtime evidence schema and ledger separation: packaged seed ledger stays immutable; runtime rows go to .buildprint/evidence/evidence-ledger.jsonl
Core capabilities

The useful parts the finished build should expose.

01 SYSTEM_MAP.md with source-backed architecture, flows, routes/services, data, integrations, side effects, tests, and unknowns
02 BUILDPRINT_CANDIDATES.md with scoped candidates and clear included/excluded surfaces
03 A selected-buildprint/ executable packet, not obsolete START_HERE/PRE_IMPLEMENTATION_QUESTIONS/03-capabilities routing
04 01-questions.md with only blocking questions and AI-best-judgment defaults
05 02-project-setup.md with product shape, architecture decisions, production readiness, implementation setup, assumptions, and phase start gate
06 03-phases/phase-flow.md plus phase files that start with ## How to implement this phase
What you need

Local first, live proof explicit.

Baseline: Nothing for public repos

  • GitHub/private repo access if the source is private
  • A human scope choice when multiple candidates exist
  • Permission to use any private source code
System shape

What kind of artifact this becomes.

Workflow surface

A repo-to-Buildprint workflow that preserves scope fidelity, generates product-led executable phase files, enforces runtime evidence honesty, embeds visual/product direction from a maintained vision guide, and proves the packet with fresh-agent replay instead of trusting a static spec.

Runtime layer

Codex/Cursor/Claude Code, optional agb start bootstrap

Build materials

Repo / System map / Candidates / Selected packet

Proof boundary

Phase-flow replay / Evidence honesty

Build scope

Included, required from you, and outside the claim.

Included
  • Repo mapping prompt for Codex, Cursor, Claude Code, or another coding agent
  • SYSTEM_MAP.md with architecture, flows, data, integrations, tests, side effects, and unknowns
  • BUILDPRINT_CANDIDATES.md with scoped reusable Buildprint options
  • A selected-buildprint/ executable packet with BUILDPRINT.md, 01-questions.md, 02-project-setup.md, blueprint.yaml, phase-index.yaml, phase-flow.md, phase files, 04-evaluation.md, and evidence schema
Bring yourself
  • GitHub/private repo access if the source is private
  • A human scope choice when multiple candidates exist
  • Permission to use any private source code
Out of scope
  • Whole-repo sludge
  • Secret leakage
  • Scope shrink
  • Hallucinated intent
Agent handoff

Start from the packet, not the UI.

agb start https://agent-buildprint.com/buildprints/buildprint-mapper-os/package.json
Agent guide Manifest GitHub files
Key files

The first files an agent should read.

BUILDPRINT.md compatibility bootstrap or package contract
All package files
acceptance.yaml machine-readable mirror
buildprint.json machine-readable mirror
BUILDPRINT.md compatibility bootstrap or package contract
checks/acceptance.md acceptance checklist
claims.yaml machine-readable mirror
CONTRACTS.md legacy interface/data contracts, when present
evals/golden-projects/admin-dashboard/.env.example evaluation harness artifact
evals/golden-projects/admin-dashboard/package.json evaluation harness artifact
evals/golden-projects/admin-dashboard/src/models/db.ts evaluation harness artifact
evals/golden-projects/large-monorepo/expected-signals.json evaluation harness artifact
evals/golden-projects/large-monorepo/package.json evaluation harness artifact
evals/golden-projects/large-monorepo/prisma/schema.prisma evaluation harness artifact
evals/golden-projects/local-rag-chat/.env.example evaluation harness artifact
evals/golden-projects/local-rag-chat/expected-signals.json evaluation harness artifact
evals/golden-projects/local-rag-chat/package.json evaluation harness artifact
evals/golden-projects/local-rag-chat/prisma/schema.prisma evaluation harness artifact
evals/golden-projects/local-rag-chat/README.md evaluation harness artifact
evals/golden-projects/local-rag-chat/src/lib/rag/ingest.ts evaluation harness artifact
evals/golden-projects/malicious-secrets/.env.example evaluation harness artifact
evals/golden-projects/malicious-secrets/package.json evaluation harness artifact
evals/golden-projects/malicious-secrets/README.md evaluation harness artifact
evals/golden-projects/malicious-secrets/src/agent.ts evaluation harness artifact
evals/golden-projects/route-patterns/.env.example evaluation harness artifact
evals/golden-projects/route-patterns/expected-signals.json evaluation harness artifact
evals/golden-projects/route-patterns/package.json evaluation harness artifact
evals/golden-projects/stripe-saas/expected-signals.json evaluation harness artifact
evals/golden-projects/stripe-saas/package.json evaluation harness artifact
evals/golden-projects/stripe-saas/src/lib/stripe.ts evaluation harness artifact
evals/golden-projects/stripe-saas/tests/billing.test.js evaluation harness artifact
evals/README.md evaluation harness artifact
HOW_TO_EVAL.md Buildprint package file
METHODOLOGY.md Buildprint package file
phases.yaml machine-readable mirror
PLAN.md legacy execution index, when present
plans/00-safety-boundaries.md phase rail
plans/01-repo-census.md phase rail
plans/02-system-map.md phase rail
plans/03-candidate-buildprints.md phase rail
plans/04-scope-decision.md phase rail
plans/05-single-extraction.md phase rail
plans/06-system-extraction.md phase rail
plans/07-validation-submission.md phase rail
policies/quality.md policy artifact
policies/questions.md policy artifact
policies/safety.md policy artifact
prompts/discover.md Buildprint package file
prompts/extract-selected.md Buildprint package file
publication.json machine-readable mirror
questions.md configuration interview
README.md human overview, non-authoritative
schemas/candidate.schema.json schema artifact
SPEC.md legacy behavior requirements, when present
templates/executable-packet/01-questions.md Buildprint package file
templates/executable-packet/02-project-setup.md Buildprint package file
templates/executable-packet/03-phases/phase-flow.md Buildprint package file
templates/executable-packet/04-evaluation.md Buildprint package file
templates/executable-packet/blueprint.yaml machine-readable mirror
templates/executable-packet/BUILDPRINT.md Buildprint package file
templates/teams/data-persistence.md Buildprint package file
templates/teams/integration-runtime.md Buildprint package file
templates/teams/product-architect.md Buildprint package file
templates/teams/security-boundary.md Buildprint package file
templates/teams/test-and-verification.md Buildprint package file
templates/teams/ux-ui-craft.md Buildprint package file
VERIFICATION.md Buildprint package file
vision.md Buildprint package file