1.4 KiB
Decision Log
Decision 001: File-first architecture
Status: Accepted
Reason:
The MVP should remain simple, local, transparent, and easy to inspect.
A database is unnecessary before the model card schema and extraction protocol are stable.
Decision 002: JSON for machine-readable model data
Status: Accepted
Reason:
JSON is easy to validate with JSON Schema and suitable for later integration into scripts, selectors, or applications.
Decision 003: Markdown for human-readable model cards
Status: Accepted
Reason:
Markdown is easier for the project owner to read, edit, and review.
Decision 004: QPI and Intellectual Archaeology as first sample models
Status: Accepted
Reason:
QPI represents a routing model.
Intellectual Archaeology represents a deep modeling model.
Together they test two different kinds of model structures.
Decision 005: Rule-based selector in v0.1
Status: Accepted
Reason:
The first selector should validate data structure and model routing logic without relying on LLM calls.
Decision 006: Use product root instead of a nested phase directory
Status: Accepted
Reason:
the-mindscape-of-bro-tsong is the product and system boundary.
model_library_mvp is the current phase and subsystem goal, not a separate root project.
The repository should not start as the-mindscape-of-bro-tsong/model_library_mvp/ because that would add unnecessary root-vs-subproject ambiguity before the product needs a monorepo layout.