Repository navigation
docs: add Loop Engineering user guide - #8
Merged
Merged
Conversation
Colin4k1024
marked this pull request as ready for review
July 17, 2026 07:31
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.
What changed
Why
The recently added Loop Engineering runtime had implementation and command documentation, but lacked a complete user-facing guide that explained when to use it and how to operate it safely across supported targets.
User impact
Users now have an executable onboarding path for
/loop-start,/goal,/heartbeat,/triage,/loop-status, and related state management. The guide also clarifies that Loop Engineering is a beta capability pack rather than a ninth team role.Validation
node scripts/validate-file-references.js --strictnode scripts/validate-doc-freshness.jsnode scripts/validate-library.jsloop-engineering