From customer demand to generated software
The governing chain is Customer Demand → Requirements → arc42 → SAS → HLD → LLD → Specifications → codegen/codemod. Each stage constrains the next. Existing source is migration evidence: useful capabilities and information must be recovered, while the design follows the requirements.
The target is a specialized MetroPlat server for personal, virtual, and executive assistance across continuing work: research, planning, coordination, computer operations, usable artifacts, evolving context, and follow-through.
Current status
The repository contains reusable journal and work-record transformations. VICTOR already renders public Markdown into a static site; that publishing capability does not demonstrate an integrated assistant. Those foundations do not yet establish the complete assistant. The design must connect them through enforceable authority and execution boundaries, shared-work coordination, and checks of outcomes where the work is received.
The specifications distinguish a proposed action, an execution attempt, its reported result, and independent acceptance of that result. A recorded operation or a settled chain transaction does not by itself establish that the user's goal was achieved.
The formal evidence model, isolated execution, shared-work resolution and EVM write path still require design and realization work. The project is early alpha, with specifications ahead of an accepted integrated implementation.
Release status
The project is being prepared for open-source release. Its license remains undecided, and no supported public package is available through this site. See the project overview and dated supplier descriptions and comparison limits.