Skip to content

EPIC: v0.2 maintenance roadmap (corrective · adaptive · perfective) #27

@hyperpolymath

Description

@hyperpolymath

Durable backlog for arghda-core v0.2, organized by ISO/IEC-14764 maintenance type × must/intend/wish. Every item ladders up to the project's two north stars: trust (a proven/ file is actually still proven — kill the silent-failure class) and reusability across provers (the language-agnostic engine consumed by arghda-panll / arghda-studio).

This issue stands in for a GitHub Milestone (none could be created via the available tooling).

Corrective — faults relative to the goal

Adaptive — adapt to provers / toolchain / estate / consumers

Perfective — quality / performance / evolvability

Recommended sequence

  1. corrective/must: transitive-import closure hashing for proven staleness #12 → 2. corrective/must: lock in cycle-safety of the import walk with a regression test #13 (both in feat(proven): transitive-import closure hashing + cycle-safety regression #26) → 3. adaptive/must: make the "language-agnostic" claim honest (Agda-first today) #16 + adaptive/must: wire the standards rsr-profile capability check into CI #17 → 4. perfective/must: version the JSON contracts + adopt SemVer #21then 5. the adaptive/intend: introduce the Language abstraction (multi-prover) + a second backend #18 Language epic for 0.2.

(Preventive-flavored items — cycle guard #13, timestamp KATs #15, contract versioning #21 — are slotted by dominant character; say the word for a separate preventive lane.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions