Fission

Fission Documentation Hub

Central index for where documentation lives and how to keep it consistent across the main repository and this GitHub Wiki.

Canonical sources (main repository)

Kind Location Notes
Contributor workflows AGENTS.md Ownership rules, crate map pointers
Architecture contracts docs/architecture/ARCHITECTURE.md System design + invariants
CLI behavior docs/CLI.md Flags, outputs—must match releases
Evaluation harness docs/EVALUATION.md External reproducibility
Release notes docs/changelog/ Immutable release history
CI/CD semantics .github/workflows/, .github/CI_CD_GUIDE.md Automation truth

GitHub Wiki (this site)

Rendered wiki: https://github.com/sjkim1127/Fission/wiki

Wiki Git repository: https://github.com/sjkim1127/Fission.wiki.git

Use the wiki for high-churn operational guidance:

Keep behavior-changing contracts in the tracked repository (docs/, .github/, AGENTS.md) so they ride alongside code review.

Where docs live (classification)

Category Canonical location Rule of thumb
Behavior / APIs / CI semantics Repository (docs/, workflows, crate docs) Requires PR review with code
Tutorials / runbooks / FAQs Wiki Fast iteration; link back to repo paths
Raw automation artifacts Repository paths (benchmark/artifacts/ conventions) Large binaries stay ignored unless curated fixtures

Wiki pages must link to concrete paths on main when referencing behavior. If wiki prose disagrees with docs/ or code, treat the wiki as stale until corrected.

Editing workflow

  1. Change docs/ or AGENTS.md whenever semantics or CLI contracts shift—those updates merge with feature PRs.
  2. Update Wiki pages when operational guidance changes (tutorial steps, screenshots narratives, onboarding rituals).
  3. Add cross-links both directions (wiki pages include Related repository docs sections; README links wiki hub).

Governance

Entry points