-
Notifications
You must be signed in to change notification settings - Fork 0
[Stage 2.1] Document deterministic context principles #62
Copy link
Copy link
Closed
Labels
area: architecturearea: docshelp wantedExtra attention is neededExtra attention is neededneed helpContribution wanted; scoped but needs implementation or research helpContribution wanted; scoped but needs implementation or research helpstage: 2.1MVP hardening and validation work before Stage 3MVP hardening and validation work before Stage 3status: readyReady for contributors to pick upReady for contributors to pick up
Description
Metadata
Metadata
Assignees
Labels
area: architecturearea: docshelp wantedExtra attention is neededExtra attention is neededneed helpContribution wanted; scoped but needs implementation or research helpContribution wanted; scoped but needs implementation or research helpstage: 2.1MVP hardening and validation work before Stage 3MVP hardening and validation work before Stage 3status: readyReady for contributors to pick upReady for contributors to pick up
Type
Fields
Give feedbackNo fields configured for issues without a type.
Goal: document the broader deterministic-context principle behind PR Maven CLI.
Related wording issue: #61.
Acceptance criteria:
- Explain that deterministic output does not depend on an LLM, loose heuristics, random ordering, network access, or subjective interpretation.
- Explain the product principle: parsing plus rules, one package manager, one failure model, one deterministic contract.
- Link the explanation from README.md, MANIFESTO.md, or docs/project-context.md where it best fits.
- go test ./... passes.