vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: archive asset-engine design-brief.md

Browse Source 
Moved docs/asset-engine/design-brief.md → docs/archive/asset-engine/design-brief.md
with a 12-line archival header pointing at the live implementation
artifacts (vh/asset-engine source, stacks/asset-engine/ deploy,
CATALOG-CONTRACT.md, services.yaml).

The brief explicitly framed itself as a pre-implementation handoff
("Hand this to a design agent before any pixels"). Implementation
shipped 2026-05-12; the brief's role is past. Kept for the design
rationale it carries (why Asset is first-class, why v1 is synchronous,
v2/v3 seam reasoning) — future contributors benefit from finding it
when wondering "why is it this way."

Surfaced by /tend-docs audit 2026-05-14.
This commit is contained in:
vh
2026-05-14 15:33:15 -07:00
parent 391244b18b
commit 54d1e7137e
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/asset-engine/design-brief.md → docs/archive/asset-engine/design-brief.md
+10
View File
@@ -1,5 +1,15 @@
# Asset Generation Engine — Design Brief
> **Archived 2026-05-14.** Describes the pre-implementation design intent
> for asset-engine. Implementation has shipped: source at
> [`vh/asset-engine`](https://gitea.phasefinal.com/vh/asset-engine),
> deployed to ana-docker via `stacks/asset-engine/`. The live catalog
> contract is [`docs/asset-engine/CATALOG-CONTRACT.md`](../../asset-engine/CATALOG-CONTRACT.md);
> the catalog itself is [`docs/asset-engine/services.yaml`](../../asset-engine/services.yaml).
> This brief is kept for the design rationale it carries (why Asset is
> a first-class entity, why v1 is synchronous, what v2/v3 seams exist),
> not as a guide to current behavior.
For an internal UI that fronts the inference services on `irv-ml1`
catalogued in [`services.yaml`](services.yaml). Hand this to a design
agent before any pixels.