Copilot/standardize document headers#13
Merged
godofthunder101 merged 137 commits intomainfrom Apr 15, 2026
Merged
Conversation
Add Purpose/Defines/Does Not Define/Authority Level/Related Documents header sections to the four target architecture and navigation docs. - CrypSA_Invariant_Boundary.md: rename Specification Authority → Authority Level; add Defines, Does Not Define, Related Documents - CrypSA_Observer_Model.md: rename Specification Authority → Authority Level; add Defines, Does Not Define, Related Documents - CrypSA_Invariants_and_Design_Space.md: add Defines, Does Not Define, Authority Level, Related Documents - How_To_Read_CrypSA.md: add Defines, Does Not Define, Authority Level, Related Documents (navigation-doc phrasing) Agent-Logs-Url: https://github.com/godofthunder101/crypsa-architecture/sessions/deef8a05-98e9-42dd-9753-729ee38e5957 Co-authored-by: godofthunder101 <17448208+godofthunder101@users.noreply.github.com>
Agent-Logs-Url: https://github.com/godofthunder101/crypsa-architecture/sessions/69ff3b39-d6d8-4133-b087-5a90eb1d5505 Co-authored-by: godofthunder101 <17448208+godofthunder101@users.noreply.github.com>
Updated section header to include an emoji for clarity.
Renamed section from 'Specification Authority' to 'Authority Level'.
Renamed section from 'Specification Authority' to 'Authority Level'.
Added implementation guidance section with example approaches for CrypSA.
Added implementation guidance section with notes on patterns and invariants.
Added implementation guidance section with notes on patterns and invariants.
Added implementation guidance section with notes on example approaches and invariants.
Added implementation guidance section with example approaches for CrypSA.
Added implementation guidance section to provide example approaches for CrypSA.
Updated language for clarity and specificity in implementation guidance and purpose sections.
Clarified the recommendation status of implementation patterns.
Clarified recommendation status of implementation patterns.
Clarified the recommendation status of implementation patterns.
Clarified recommendation status for implementation patterns.
Clarified recommendation status of implementation patterns.
Updated document structure and terminology definitions for clarity and organization.
Clarify documentation on CrypSA boundaries and state.
Updated terminology and clarified definitions related to architecture and canonical event history.
Removed redundant text and added a note about the canonical event history.
Refine the description of the core runtime loop and clarify the roles of observers and validators. Update terminology for consistency and enhance the explanation of canonical event history.
Refine language for clarity and consistency throughout the document, including updates to the validator's role and minimal runtime components.
Updated the CrypSA architecture overview to clarify the roles and responsibilities of various components, including the validator, adapters, and lenses. Enhanced the explanation of data flow and intent flow.
Clarified definitions and responsibilities regarding the authority level, adapters, and lenses. Added references to CrypSA_Boundary_Definitions.md for strict responsibility boundaries.
Clarified definitions regarding runtime behavior and canonical events. Updated language for consistency and precision throughout the document.
Updated the document to define core terms and structure of CrypSA, enhancing clarity and consistency across terminology.
Updated terminology and clarified the relationship between diagrams and authoritative definitions.
Updated terminology and phrasing for clarity and consistency in the CONTRIBUTING.md file.
This document outlines the implications of the CrypSA architecture on infrastructure, detailing shifts in responsibilities, changes in state representation, and new considerations for system design.
Added a reference to infrastructure implications and clarified data flow.
Added new section on infrastructure implications and updated build instructions.
Updated terminology for clarity and added reference to infrastructure implications.
Added reference to infrastructure design implications.
Added reference to CrypSA's infrastructure implications and updated local simulation to local prediction in the experience section.
Clarified the validator's role in event processing.
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.
Pull Request Checklist
Please confirm the following before submitting your PR.
🧠 Understanding
CONTRIBUTING.md🔒 Authority Rules
spec/🧠 Terminology
CrypSA_Terminology_Primer.md🔐 Canonical Phrasing (Required)
I used the exact canonical phrases where applicable:
🧱 Architectural Boundaries
I did not blur boundaries between:
I did not introduce logic into the wrong layer
📚 Documentation Discipline
🧪 Scope of Change
OR
🚫 Final Check
Summary
Briefly describe your change:
(Write here)