← Back to registry
Mapped Project Advanced by Agent Buildprint

Portable AI Shorts Production Studio

A Mapper OS executable packet that preserves the full AI shorts production workflow while keeping provider, media, browser, persistence, gallery, publishing, and security claims tied to phase proof and runtime evidence.

Open manifest GitHub folder

methodology

agent-ready
01 Setup gate
02 Phase-flow execution
03 Runtime evidence ledger
04 Claim-safe validation

Executable packet spine

The files or runtime artifacts a fresh agent must read or produce before claiming progress.

  • BUILDPRINT.md
  • 01-questions.md
  • 02-project-setup.md
  • blueprint.yaml
  • 03-phases/phase-index.yaml
  • 03-phases/phase-flow.md
  • 03-phases/<active-phase>.md
  • 04-evaluation.md
  • 05-evidence/evidence-ledger.schema.json
  • .buildprint/phase-runs/<phase-id>/proof.md
  • .buildprint/evidence/evidence-ledger.jsonl

Proof gates

Checks that prevent a vague implementation from being reported as complete.

  • ✓Mapper OS selected-output spine exists and starts from BUILDPRINT.md
  • ✓Every phase starts with the required Mapper OS phase implementation heading
  • ✓Every phase requires phase-flow, .buildprint/next-agent.md, and current project AGENTS.md
  • ✓02-project-setup.md defines architecture, team operating model, execution authority, delegation, AGENTS.md plan, quality gates, safety, assumptions, and phase start gate
  • ✓Packaged evidence ledger is seed-only and runtime evidence routes to .buildprint/evidence/evidence-ledger.jsonl
  • ✓Evidence schema requires artifact_id, type, phase_id, status, source, proves, proof_type, provider_mode, and upgrades_claim
  • ✓Blocked, missing, synthetic, partial, sandbox-limited, network-limited, credential-limited, or dry-run proof cannot upgrade claims
  • ✓Browser, provider, media, persistence, billing-free publishing handoff, security, memory/retrieval-adjacent context, and operational boundaries are preserved as explicit contracts

Risks covered

Failure modes the Buildprint makes visible before an agent can hide them in “done”.

  • ⚠Accidentally implying OpenShorts clone or drop-in replacement parity
  • ⚠Provider/API/live media success overclaiming
  • ⚠Rendering-quality parity overclaiming
  • ⚠Social platform publishing reliability overclaiming
  • ⚠Public gallery exposure without consent and access controls
  • ⚠User likeness, uploaded media, URL egress, and copyright under-specification
  • ⚠In-memory proof storage being misreported as production durability

What this ships

01

BUILDPRINT.md canonical start

02

01-questions.md AI best-judgment alignment gate

03

02-project-setup.md with architecture, team model, AGENTS.md plan, safety, gates, and phase start gate

04

blueprint.yaml executable-blueprint v5 machine contract

05

03-phases/phase-flow.md orchestration protocol

06

Five implementation phase files

07

04-evaluation.md claim upgrade rules

08

05-evidence/evidence-ledger.schema.json honest evidence schema

09

Seed-only 05-evidence/evidence-ledger.jsonl

10

Compatibility docs for specification, contracts, plan, test matrix, validation, and acceptance

Validation evidence

For newer phase-flow Buildprints, this names replay or outcome evidence. For older registry entries, it lists the included validation checks.

  • Phase-flow executable packet with proof-gated implementation phases.
  • Seed evidence is separated from runtime proof and blockers cannot upgrade claims.
  • Default proof uses deterministic no-network adapters; live providers are optional and gated.
  • OpenShorts-inspired scope is preserved without claiming clone, provider, rendering, or publishing parity.

Copyable agent prompt

Manifest 
Use the Portable AI Shorts Production Studio Buildprint. First bootstrap exact snapshots: agb start https://agent-buildprint.com/buildprints/portable-ai-shorts-production-studio/package.json . If agb is not installed, clone https://github.com/DomEscobar/agent-buildprint and run node agent-buildprint/bin/agb.js start https://agent-buildprint.com/buildprints/portable-ai-shorts-production-studio/package.json . Then read BUILDPRINT.md, 01-questions.md, 02-project-setup.md, blueprint.yaml, 03-phases/phase-index.yaml, 03-phases/phase-flow.md, the active phase file, 04-evaluation.md, and 05-evidence/evidence-ledger.jsonl. Use Mapper OS phase-flow artifacts before implementation and write runtime evidence only to .buildprint/evidence/evidence-ledger.jsonl. Build the full browser AI shorts production studio proof with deterministic mock/no-network providers, pollable jobs, a playable 1080x1920 MP4 fixture, private gallery, consent-gated publish handoff, browser QA, and honest claim boundaries.