scrapup
AI-assisted Unified Process
BETA · COMING SOON
PLUGIN FOR CLAUDE CODE — DOCUMENT → VALIDATE → DELIVER
From informational scrap to forged delivery.
An ecosystem of skills, agents, and commands for Claude Code that operationalizes the document → validate → deliver cycle with engineering rigor — a modernized, AI-assisted Unified Process.
The developer moves from executor to architect and validator — agents run the engineering workflows; the human decides and seals.
// 01 — THE PROBLEM
AI is fast. Left unsupervised, it's fragile.
Iterating with AI and no human in the loop degrades security and reliability — and spec scaffolding alone does not guarantee the agent follows it.
+37.6%
critical vulnerabilities after five AI refinement iterations — "feedback-loop security degradation."
arXiv 2506.11022
500k+
samples analyzed — AI-generated code carries more high-risk vulnerabilities than human-written code.
arXiv 2508.21634
Scaffolding alone isn't enough.
Even with templates and checklists, agents skip instructions. Independent verification is required.
martinfowler.com · ACM TechBrief 2026
// 02 — THE ANSWER
Agents execute. Humans seal the gates.
scrapup turns AI from a fast-and-fragile code generator into a governed engineering process — a traceable, auditable contract from intent to production.
01
document
Every feature derives from a versioned spec, not a loose prompt.
02
validate
Multi-lens review — quality, security, architecture — before concluding.
03
deliver
Nothing is done without observable, evidence-backed verification.
// 03 — HOW IT WORKS
The four-phase spine.
Each phase closes at a milestone a human Validator seals. Construction shrinks; judgment migrates to Inception and Elaboration.
LCO
Inception
Scope, actors, candidate architecture, critical risks.
LCA
Elaboration
Executable architectural baseline; risks mitigated.
NOW · BETA
IOC
Construction
First public release — ready for beta in your environment.
RELEASE
Transition
Running in production; verified by telemetry.
RETAINED HUMAN ROLE · 01
The Architect
Owns architecture-centric decisions: defines and validates the architecture, approves the executable baseline, fixes constraints.
RETAINED HUMAN ROLE · 02
The Validator
Owns quality and verification: adjudicates the review lenses, decides risk ordering, seals each milestone.
The AI proposes and verifies. The human decides and seals.
// 04 — FOUR PILLARS
What scrapup gives you.
P1
Traceable & auditable, end-to-end
Intent → spec → code → test → commit → release. Features derive from versioned specs (SDD).
P2
Human-sealed milestone gates
Risk-driven LCO → LCA → IOC → Release. Nothing advances without sign-off.
P3
Multi-lens validation
Independent review from multiple perspectives before anything is "done." Evidence required.
P4
Open & extensible by default
Git, MCP, PlantUML, markdown — no proprietary lock-in.
// 05 — WHY IT'S DIFFERENT
Spec-as-contract is the floor.
GitHub Spec Kit, Amazon Kiro, Superpowers, Tessl — all converge on spec-as-contract. The real question is no longer which model writes better code, but which process maintains context, traceability, and control.
THE FLOOR — WHAT PEERS DO
Spec-as-contract. Without a classical engineering foundation, frameworks just institutionalize vibe coding under new terminology.
SCRAPUP'S EDGE
The control the evidence demands — human-sealed, risk-driven milestone gates plus multi-lens validation, anchored in the Unified Process.
// 06 — BUILT ON THE UNIFIED PROCESS
Classical engineering, applied to a new medium.
The Unified Process (Jacobson, Booch, Rumbaugh, 1999) supplies a foundation no competitor explicitly claims. Its pillars stay immutable — only who does the work changes.
use-case drivenarchitecture-centriciterative & incrementalrisk-driven
Workers become dispatchable agents — canonical UP tailoring, not a rupture.
// 07 — OPEN & EXTENSIBLE
No lock-in. Three axes of extension.
Composable pieces
Skills, agents, and review lenses you can add, swap, or remove.
Tailorable process
Lean increment → full flow. Ceremony scales to risk, never bureaucracy.
Open integrations
Built on the open stack — no closed proprietary UI in the way.
gitmcpplantumlmarkdown MIT license
// 08 — STATUS
Beta — and honest about it.
● SHIPPED NOW
Solo-usable Beta
Multi-lens review
Lean increment flow
Open tooling (Git / MCP / markdown)
○ ON THE ROADMAP
Team-scale governance
Sealed LCA gate · risk-ordered iterations
Traceability matrix
Transition via telemetry
// 09 — FOLLOW THE BUILD
Forge with us.
scrapup is solo-usable Beta today. Star the repo to follow the build from Beta to Release, or read the docs to see the process in full.
Follow the build.
Open-source, MIT-licensed. Star the repo to track each milestone, or read the docs to see the process in full.
scrap → forge → forged delivery