Skip to content
This repository was archived by the owner on Sep 13, 2025. It is now read-only.

MATURITY.md

Latest commit

 

History

History
49 lines (32 loc) · 1.78 KB

MATURITY.md

File metadata and controls

49 lines (32 loc) · 1.78 KB
Raw

✅ AnswerCite Repo Maturity Checklist

This checklist helps ensure each AnswerCite module meets our standards for operational hygiene, symbolic trust, and contributor clarity. Repos should aim to satisfy these signals before public release or external contribution.

🧩 Core Hygiene

  • README.md clearly states purpose, usage, and trust philosophy
  • status.json endpoint reflects uptime, version, and governance signals
  • LICENSE file is present and appropriate for open-source use
  • CODEOWNERS defines escalation and ownership logic
  • SECURITY.md outlines disclosure policy and anomaly flag triggers
  • CONTRIBUTING.md is present or inherited from org-level defaults

🛡️ Trust Signaling

  • SVG trust badge available or planned (/badge.svg)
  • Anomaly flags or hygiene scores implemented (if applicable)
  • Schema validation logic included or referenced
  • Public API or interface documented in /docs or README
  • No vendor lock-in or opaque dependencies

📣 Contributor Clarity

  • Issues enabled with hygiene-first labels (trust-signal, schema, anomaly)
  • Optional project board for roadmap or MVP tracking
  • Clear onboarding path for new contributors
  • Escalation paths documented via CODEOWNERS or status metadata

🧪 Experimental Modules

Experimental repos may bypass some scaffolds but must include:

  • README.md with experimental disclaimer
  • status.json with version and contact metadata
  • Clear label (experimental, prototype) in repo name or description

🧠 Symbolic UX

AnswerCite modules are more than code—they’re trust signals. Every repo should reflect our commitment to clarity, autonomy, and governance-aware design.