86 lines
2.7 KiB
Markdown
86 lines
2.7 KiB
Markdown
# 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.
|
|
|
|
## Decision 007: Use supplier request channels for CCPE and skills-vault
|
|
|
|
Status: Accepted
|
|
|
|
Reason:
|
|
|
|
This repository is a product and application workspace. It should not silently absorb expert-agent specification work or reusable automation Skill source work.
|
|
|
|
Requests for agents, runtimes, model governance, invocation protocols, evaluation rules, and integration registrations should be recorded under `requirements/ccpe/`.
|
|
|
|
Requests for deterministic reusable automation tools and installable Skills should be recorded under `requirements/skills-vault/`.
|
|
|
|
If a supplier capability blocks model extraction, the dependent extraction step should pause unless the project owner explicitly says to solve the need locally.
|
|
|
|
## Decision 008: Third-party frameworks belong to product implementation, not CCPE or skills-vault
|
|
|
|
Status: Accepted
|
|
|
|
Reason:
|
|
|
|
Frameworks such as CrewAI and LangGraph may be useful later for implementing product behavior. The concrete application adapters, state, deployment, and product runtime belong in this repository.
|
|
|
|
CCPE may define the agent contract, runtime governance, authority, evaluation, and integration registration.
|
|
|
|
skills-vault may provide reusable deterministic helper Skills discovered during implementation.
|