create-architecture

> STOP. READ THIS ENTIRE SKILL.MD BEFORE CALLING ANY ENDPOINT. # create-architecture Create architecture diagrams from pipeline definitions. Generates Excalidraw-compatible elements with labeled shapes, connecting arrows, and file attachments. ## Usage ```bash # Create from a YAML pipeline definition ./run.sh create --input pipeline.yaml --presentation-only # Deadline-bound implementation architecture ./run.sh create --input pipeline.yaml --execution-locked --execution-gate gate.json # Create from inline JSON ./run.sh create --name "QuerySpec Pipeline" --json '[{"id":"step1","label":"Classifier","tech":"SetFit"}]' --presentation-only # Add a component to an existing architecture ./run.sh add-component --project queryspec-pipeline --label "New Step" --after recall --presentation-only # List saved architectures ./run.sh list ``` ## Pipeline YAML Format ```yaml name: "QuerySpec Pipeline" components: - id: omnibar label: Omnibar tech: "React input" latency: "0ms" color: purple # purple|green|blue|amber|red files: - packages/ux-lab/src/components/binary-explorer/BinaryExplorerView.tsx - id: intent label: Intent Classifier tech: "SetFit 0.5B" latency: "<10ms" color: green files: - src/graph_memory/intent/_t05.py connections: - from: omnibar to: intent ``` ## How It Works 1. Parses pipeline definition (YAML or JSON) 2. Generates Excalidraw elements: rectangles with bound text labels, arrows with bindings 3. Lays out components vertically with consistent spacing 4. Saves via `PUT /api/architecture/:id` on the UX Lab Express server 5. Architecture appears at `localhost:3002/#architecture` ## Execution-Locked Architectures When the user names a deadline, runnable campaign, immediate operational target, or reports drift, implementation workflow diagrams must use `--execution-locked`. The YAML must classify every component: ```yaml execution_lock: objective: "Start the executable regression campaign tonight" deadline: "2026-07-13T23:59:00-04:00" current_phase: corpus critical_path: [corpus, model, physical_canary, campaign] deferred: [release_qualification, expanded_suite] stop_condition: "Campaign process starts and writes its first live row receipt" max_attempts_per_blocker: 2 max_identical_failures_per_family: 3 systemic_failure_action: stop_family_mark_remaining_blocked_continue_independent_families reviewer_scope_authority: none update_interval_minutes: 5 ``` The runtime rejects missing fields, unclassified components, overlap between critical and deferred work, an off-path current phase, more than two attempts per blocker, more than three identical failures in one family, any systemic failure action other than family-level fail-fast, reviewer scope authority, or an update interval over five minutes. An architecture may show deferred work, but the project agent may not execute it before the critical-path stop condition without explicit user authorization. For campaigns, three identical failed gates, error codes, or root causes make the family systemic. Stop that family, preserve representative evidence, mark untouched variants `blocked_by_systemic_failure`, and continue independent families. Do not add retry loops, qualification rungs, architecture work, or adjacent components to make the diagram appear comprehensive. The architecture must keep the human's objective unchanged; reviewer recommendations cannot move components from deferred work onto the critical path. ## Mutation Authorization Gate `create` and `add-component` reject mutation unless one mode is explicit: 1. `--presentation-only`, which labels the saved diagram as non-evidence. 2. `--execution-gate gate.json`, where a human-authored gate contains: ```json { "gate_id": "current-gate", "status": "BLOCKED_CURRENT_GATE", "architecture_authorized": true } ``` Missing, malformed, or unauthorized gates fail before any API request with `REJECTED_SCOPE_EXPANSION`. A project agent must not set `architecture_authorized:true` on the human's behalf. ## Colors | Name | Hex | Use | |------|-----|-----| | purple | #7c3aed | UI/frontend components | | green | #00ff88 | Deterministic/verified steps | | blue | #4a9eff | Search/retrieval steps | | amber | #ffaa00 | LLM/model inference steps | | red | #ff4444 | Error/warning states |