Skip to content

Roadmap

Jeremy Longworth edited this page Sep 12, 2026 · 2 revisions

Roadmap

AgentCannabis v1.0 is complete against the supplied Canadian Cannabis Skill Repository roadmap. The project is now in maintenance and evidence-refresh mode; future changes should be proposed as scoped follow-on work rather than quietly changing the v1 contracts.

Release criteria

The v1 acceptance criteria cover:

  • traceable evidence for CC-00 through CC-39;
  • the frozen 233-skill Master Taxonomy v1.0;
  • 18 professional skillsets built from self-contained packages;
  • explicit scope, safety, source-currentness, and human-authority boundaries;
  • structural, review-gate, forward, integrated, adversarial, and install validation;
  • public repository and GitHub wiki publication; and
  • successful public release-tag installation for all 18 professional wrappers.

Evidence files

  • ROADMAP.md — development authority and wave contracts;
  • docs/development/wave-status.json — machine-readable wave status;
  • docs/development/acceptance-criteria.md — release requirements;
  • docs/development/CC-39-final-audit.md — current readiness decision;
  • docs/development/evaluations/CC-10-forward-test.md — reference-skill test;
  • docs/development/evaluations/CC-35-integrated-workflows.md — integrated cases;
  • docs/development/evaluations/CC-36-adversarial-evaluations.md — boundary cases; and
  • docs/development/peer-consistency-review.md — comparison with peer repos.

Maintenance priorities

  1. Reverify high-change legal, regulatory, tax, quality, and safety sources.
  2. Keep the exact taxonomy, manifests, generated packages, and routing files synchronized.
  3. Add captured evaluation evidence when behavior changes; scenario files alone are not behavioral proof.
  4. Re-run public install checks when packaging, metadata, or release tags change.
  5. Keep README and wiki commands aligned with the installed GitHub CLI and supported host behavior.

Current decision

V1_READY means repository artifacts, validation gates, public repository state, wiki content, and installability evidence are complete. It does not mean every future response from every host is legally correct, current for a specific site, or professionally approved.

Clone this wiki locally