Events 109-112: pi.dev comparison response (Tier 1 doc fixes + Tier 2 features + Tier 3 partial schema + hot-reload)#73
Merged
Conversation
The pi.dev architectural comparison analysis is private analytical content with no codebase-side reader. Moving it out of the public tree under the operator's idea_analysis/ category in the private filesystem (per Event 66 Tier 1 privatization pattern; plain mv since no symlink needed for a doc with no public reader).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
Four bundled Events shipped as one PR — all reversible, additive, and conceptually unified as the response to the pi.dev architectural comparison.
docs/LAYER_MODEL.mdsplitting cognition portability from enforcement portability. Layer-explicit hero tagline inREADME.md+web/src/components/site/Hero.tsx: "There are many agent harnesses.epistemeis the cognition layer that runs above them all." Corpus inventory inkernel/README.mdclassifying all 18 kernel/*.md.examples/checks/directory (README + 3 example checks). Blueprint D schema extension:POSTURE_VALUES += analysis,BLAST_RADIUS_STATUS_VALUES += deferred,_validate_deferred_discoveriesrelaxed. CHANGELOG entry. Two design specs:docs/SPEC_RIGOR_KNOB.md+docs/SPEC_REASONING_SURFACE_BRANCHING.md.episteme check new <name>scaffolder with 3 vendored templates.episteme status [--watch] [--json]runtime-state TUI.episteme dev watch [--once|--continuous]poll-based source-to-plugin-cache file watcher with atomic-copy + syntax-validation guard — closes the F3 friction loop.Verification
pytest -q tests/ --ignore=tests/test_session_context_noise_watch.py→ 834 passed + 35 subtests in 5.50s. Zero regressions across all four Events (was 766 + 21 baseline; +68 net new tests).episteme check new probe-test,episteme status --json,episteme dev watch --once --target=<tmpdir>(33/33 files copied).Test plan
episteme dev watch --oncefrom project root after merge → confirms plugin cache picks up new validatorSoak invariant
Zero touches to: kernel/CONSTITUTION.md, kernel/REASONING_SURFACE.md, kernel/FAILURE_MODES.md, core/hooks/* (other than _blueprint_d.py per Event 110), core/blueprints/* (other than architectural_cascade.yaml comment polish per Event 110), templates/, labs/, hooks/hooks.json. The only touch to the live gate enforcement is the operator-explicitly-authorized Tier 3 partial schema extension in Event 110.
Squash-merge recommended; branch carries chkpt-commit audit trail.