Skip to content

docs: specify certified declarative JSON symmetry - #135

Merged
SamuelIVX merged 1 commit into
mainfrom
docs/declarative-symmetry-specs
Nov 12, 2026
Merged

SamuelIVX merged 1 commit into
mainfrom
docs/declarative-symmetry-specs

Conversation

@SamuelIVX

Copy link
Copy Markdown
Owner

Summary

Define B10's approved extension: certify declarative JSON for symmetry across DFS, static POR, DPOR and CBS with exact HASHED/ORDERED and approximate BITSTATE storage. This PR contains specifications and tracking updates only; implementation has not started.

Validation

  • Two completed CodeRabbit CLI reviews: Spec 92/contract initially returned three Major findings; all were independently checked and addressed. The second review covered all five final documents and returned zero findings. Actual review evidence recorded with agent-setup.
  • Separate fresh-reader passes for each spec; viewer production ownership and empty-owner rejection clarified.
  • Canonical template sections, R1–R8 mappings, tagged current-state claims, 121 relative links/anchors, 17 existing production Java scope paths, table structure and git diff whitespace pass.
  • Independent finite semaphore 8 concrete / 5 orbit and counter 16 / 5 examples cross-checked outside Java by two routes.
  • Java/build/Javadoc, PIT and browser suites were not run: this changes documentation only. Each implementation spec requires fresh baselines and its full applicable runtime/mutation/consumer gates.

Boundaries and tradeoffs

Private loader-held certification prevents public/same-package constructor bypass; reassembled objects still satisfy model-wide limits. JSON retains its existing guards, ordered effects, failed-attempt semantics and non-source identity. Final-only properties retain conservative exhaustive fallback. Precision and INCOMPLETE handling reach production viewer normalization without extending source-only resource-prefix authentication or cutoff simplification. No new generic certificate/replay interface, model family, cap increase or performance/coverage guarantee.

Co-authored-by: Codex noreply@openai.com

Define B10 certification, exact and approximate release phases, independent oracles, consumer behavior and rollback gates. Keep implementation explicitly pending and deferred work excluded.

Co-authored-by: Codex <noreply@openai.com>
@coderabbitai

coderabbitai Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Added planning documentation for certified declarative JSON symmetry, covering a staged rollout for exact and approximate support across four strategies.
    • Added specifications outlining planned behavior, compatibility constraints, acceptance criteria, and verification requirements. Implementation and new verification have not started.
    • Updated roadmap and follow-up documents to mark this work as selected and describe its planned sequence.

The pull request adds a planning contract and Specs 92 and 93 for certified declarative JSON symmetry. The documents define exact and approximate implementation phases, their constraints, and verification gates. They state that implementation and runtime verification have not started.

Changes: Declarative Symmetry

Layer / File(s) Summary
B10 scope and phase boundaries
docs/plans/declarative-symmetry-contract.md, docs/plans/future-work.md, docs/plans/post-task10-follow-ups.md
The plan selects B10 for declarative JSON symmetry and separates exact L1 work from approximate L2 work. It records that Specs 92 and 93 are drafted and implementation has not started.
Certification and exact symmetry
docs/plans/declarative-symmetry-contract.md, docs/specs/active/92-certified-declarative-symmetry.md
The contract and Spec 92 describe loader-issued certification, model and AST bounds, grouping and execution constraints, and exact strategy routing.
Approximate symmetry and result handling
docs/plans/declarative-symmetry-contract.md, docs/specs/active/93-approximate-declarative-symmetry.md
The contract and Spec 93 describe approximate membership, filtering and CBS limits, verdicts, positive-witness checks, and result handling. Spec 93 depends on L1 being implemented and merged.
Verification and completion requirements
docs/plans/declarative-symmetry-contract.md
The contract lists verification gates, review and publication procedures, authoring checks, and completion conditions. It distinguishes specification review from implementation verification.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Other

Possibly related PRs

Merge Risk: Minimal · up to 6a792

This documentation-only change defines the planned declarative symmetry work and does not alter runtime behavior. No merge-blocking risk remains.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title "docs: specify certified declarative JSON symmetry" matches the main change. The PR adds planning and specification documents (B10 contract, Specs 92 and 93, and tracking updates) for certif…
Description check Passed The description summarizes the PR. It states that the PR contains specifications and tracking updates only, with no implementation. It links the B10 contract and Specs 92 and 93, describes L1 and L2 p…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title "docs: specify certified declarative JSON symmetry" matches the main change. The PR adds planning and specification documents (B10 contract, Specs 92 and 93, and tracking updates) for certifying declarative JSON models for symmetry reduction. It does not implement code, and the title says so with the "docs:" prefix and the word "specify".

Full details: Description check

Explanation

The description summarizes the PR. It states that the PR contains specifications and tracking updates only, with no implementation. It links the B10 contract and Specs 92 and 93, describes L1 and L2 phases, and lists validation performed, including CodeRabbit reviews, link and structure checks, and the Java and runtime suites that were not run. It is directly related to the changeset.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between b1c7586 and 6a792ff.

Files selected for processing: 5

  • docs/plans/declarative-symmetry-contract.md
  • docs/plans/future-work.md
  • docs/plans/post-task10-follow-ups.md
  • docs/specs/active/92-certified-declarative-symmetry.md
  • docs/specs/active/93-approximate-declarative-symmetry.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 2

  • GitHub Check: CodeRabbit
  • GitHub Check: Mutation
Additional context used

Path-based instructions: 2

Check documented behavior, examples, commands, configuration, and requirements against implementation and available evidence.

CodeRabbit configuration file

Files:

  • docs/specs/active/92-certified-declarative-symmetry.md
  • docs/plans/post-task10-follow-ups.md
  • docs/specs/active/93-approximate-declarative-symmetry.md
  • docs/plans/future-work.md
  • docs/plans/declarative-symmetry-contract.md
Prioritize correctness, security, data integrity, and user-visible regressions.

CodeRabbit configuration file

Files:

  • docs/specs/active/92-certified-declarative-symmetry.md
  • docs/plans/post-task10-follow-ups.md
  • docs/specs/active/93-approximate-declarative-symmetry.md
  • docs/plans/future-work.md
  • docs/plans/declarative-symmetry-contract.md
LanguageTool

docs/specs/active/92-certified-declarative-symmetry.md

[uncategorized] ~33-~33: The official name of this software platform is spelled with a capital “H”.
Context: ...r normalization/browser fixtures and .github/workflows/build.yml only for complete e...

(GITHUB)

docs/specs/active/93-approximate-declarative-symmetry.md

[uncategorized] ~32-~32: The official name of this software platform is spelled with a capital “H”.
Context: ...eck.mjs, docs/visualizer-e2e.mjs and .github/workflows/build.yml for real final-matr...

(GITHUB)

[style] ~170-~170: Using “real” as an adverb is considered informal. Consider using “really” or “very”.
Context: ...patch. Forced-collision fixtures assert real positive witnesses and truthful metadat...

(REAL_REALLY)

docs/plans/declarative-symmetry-contract.md

[grammar] ~74-~74: Use a hyphen to join words.
Context: ...r and cost dominance. The existing DPOR checked sleep lookup/all-asleep normaliz...

(QB_NEW_EN_HYPHEN)

@github-actions

Copy link
Copy Markdown

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@SamuelIVX
SamuelIVX marked this pull request as ready for review November 12, 2026 15:12
@graphify-labs

graphify-labs Bot commented Nov 12, 2026

Copy link
Copy Markdown

Graphify reviews are paused for this workspace because nobody has used it in 7 days. A workspace owner can resume reviews from the Repositories page: https://app.graphify.com/personal-1d9554/repositories

@SamuelIVX
SamuelIVX merged commit c8ee553 into main Nov 12, 2026
11 checks passed
@SamuelIVX
SamuelIVX deleted the docs/declarative-symmetry-specs branch November 12, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant