IMP-063: Explain public docs through requirements and composition - #18
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs currently define OpenProse primarily as standing outcomes and tell agent readers to use retired
Services/Ensuressyntax. This change explains contract authoring as expressing intent by composing requirements, including required results, steps, limits, discretion, and evidence./declare-outcomesURL and aliases for changed heading anchors.runtime_contract: 2) atopenprose/prose@770cebc9e03a7150a73bd454b7a6da307595ff9d. Retain its five kinds, Forme/VM/ProseScript roles, and syntax. Fenced MDX examples and vendored source bytes are unchanged; older snapshot headings are explicitly identified with a link to current sources.docs.prose.mdURL, and exact content digest, together with its generation source and existing URL check. README now identifies the retained legacy.prosemaintenance programs and the model-basedprebuildhook accurately.This is an editorial and onboarding change. The agent-readable getting-started guide now teaches existing 0.18 syntax, which affects guidance consumed by readers, but adds no runtime implementation, grammar, roles, or compatibility promise. No release, deployment, consumer upgrade, or model execution was performed.
Validation at
55772b50c722233fef40b538be7f70548b7aec3c, based onmain@6b0f7dc13b2613f6548a45c96b35889802b6a2cb:pnpm exec next buildpassed in public and preview modes; standalone HTTP smoke checks passed 44/44 public and 42/42 preview.Builds retain the existing Turbopack whole-project tracing warning. The initial host-default pnpm 11 install was incompatible with the repository's script-approval setup; its incidental config edit was reverted and checks used pnpm 10.34.5. The model-based
pnpm buildprebuild hook was not run: it invokes retained legacy maintenance programs requiring a separate compatibility update. Static/site checks do not establish OpenProse execution equivalence or close the documented harness gaps.Task: IMP-063. Companions: public Site copy, company Site, core authoring reference. The public skill companion is openprose/prose#186. This docs change is based directly on current main and does not require those PRs for a successful build.
Final Verify and CodeQL checks passed. Independent review at
55772b50c722233fef40b538be7f70548b7aec3cfound no unresolved findings, including focused test, digest, preserved-example, link and rendering checks. Retained review record (workspace access required).