← Back to registry
Workflow OS Advanced by Agent Buildprint

Perfect RAG / Retrieval OS

A fresh agent can run the packet from BUILDPRINT.md through phase-flow to implement a permission-safe, citation-grounded retrieval system without reducing the product to vector search plus a prompt.

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 structural check passes
  • ✓Packet uses BUILDPRINT.md as canonical start
  • ✓Every phase starts with Mapper OS phase-flow entry grammar
  • ✓Runtime evidence is separated from packaged seed evidence
  • ✓Evidence schema blocks missing, blocked, synthetic, partial, sandbox, network-limited, and credential-limited rows from upgrading claims
  • ✓Publication copy reflects phase-flow methodology rather than legacy proof-only package

Risks covered

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

  • ⚠Vector-only false confidence
  • ⚠Hallucinated uncited answers
  • ⚠Permission leakage
  • ⚠Eval-free quality drift
  • ⚠Reranker latency/cost creep
  • ⚠Live provider claims from deterministic proof
  • ⚠Advanced-tech hype without measured gain

What this ships

01

BUILDPRINT.md canonical start

02

01-questions.md alignment gate

03

02-project-setup.md architecture, team, authority, handoff, AGENTS.md, quality, safety, and phase-start contract

04

blueprint.yaml executable-blueprint v5 machine contract

05

03-phases/phase-flow.md orchestration protocol

06

Four implementation phases with proof gates

07

04-evaluation.md retrieval, answer, operational, blocker, and claim-upgrade rules

08

05-evidence seed ledger and runtime evidence schema

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 packet with setup gate, role handoffs, proof gates, and evidence honesty.
  • The packet explicitly rejects vector-only RAG and requires measurable retrieval behavior.
  • Deterministic proof mode is separated from live embedding, search, reranker, and generator claims.
  • Tenant/private filtering is a server-side proof gate before context packing and answer generation.

Copyable agent prompt

Manifest 
Use the Perfect RAG / Retrieval OS Buildprint as a Mapper OS phase-flow packet. Start at BUILDPRINT.md, then read 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 the seed evidence schema. Complete setup before phase work, create .buildprint phase-run artifacts, and append runtime evidence only to .buildprint/evidence/evidence-ledger.jsonl. Implement corpus contracts, ingestion/chunking/indexing, hybrid lexical/sparse plus dense retrieval, fusion/dedupe, permission filtering before context packing, reranking, token-budgeted grounded answers with citations, insufficient-evidence refusal, traces, and eval gates. Use deterministic proof mode unless live providers are explicitly configured and separately proven. Do not call vector-only retrieval complete.