PanSphaira documentation
Start with the idea, follow one example, then inspect the evidence behind it. The project README is the short entry point; the reference documents retain the exact technical rules.
Start
- Overview: why adapt software around business needs, and what the ecosystem connects.
- Application guide: incoming invoices, connected analysis and provider adaptation, with distinct evidence boundaries.
- Quickstart: prerequisites, source and release identities, the local demo and owned cleanup.
Understand
- Architecture tour: responsibilities and the path from a proposed action to an observed result.
- Knowledge and reuse: sources, assumptions, negative results and qualification before reuse.
- Research questions: questions to investigate, not capabilities asserted as solved.
Verify
- Capabilities and maturity: inspect each capability in its declared scope.
- Canon and Architecture: normative rules and the technical design.
- Security assurance and Known limitations: scoped claims, dated evidence and external requirements.
- Release governance: why source, runnable artifacts and execution evidence must not be conflated.
- HMI/Harness entry points: authority-free contribution preflight; no submission, publication, external write or activation from a preflight result.
- Published releases: exact release identities, artifacts and evidence.
Extend
- Contributing: propose a change or reusable component with its tests and applicability.
- Governed Knowledge Harvest: the exact qualification and promotion rules.
- Roadmap: development direction, separately from delivered proofs.
- Discussions: questions, critique and collaboration.
The explanation pages provide a reading route; they do not replace or silently revise the canonical contracts. A historical evidence snapshot remains historical even when linked from a new page.