Conversation
…ith v2 canonicals (Event 77) CP-EXAMPLES-SCHEMA-PARITY-01 (v1.0.1 polish mini-batch CP #3). After Events 65/66/71 privatized the maintainer's canonical profile files, fork-onboarding via `episteme init` was seeding stale templates that didn't match the v2 schema. Specifically (sizes pre-fix vs canonicals): - operator_profile.example.md 1.6KB / 0 axes (canonical 10.4KB / 16 axes) — severe - cognitive_profile.example.md 8.2KB / 4 sections (canonical 10.3KB / 7 sections) — moderate - workflow_policy.example.md 2.5KB / 10 sections (canonical 3.1KB / 7 sections) — structural drift - agent_feedback.example.md DOES NOT EXIST (canonical 10.9KB / 3 sections) — total gap Fork users running `episteme init` now seed schema-faithful templates: - operator_profile.example.md — full v2 schema scaffolding (6 process axes + 9 cognitive-style axes + expertise_map = 16 total). Each axis carries the per-axis metadata structure (value / confidence / last_observed / evidence_refs / note) with confidence:stub default and inline notes teaching the value range / enum + the kernel mechanism that consumes it. - cognitive_profile.example.md — adds 3 missing sections (Decision Engine, Cognitive Red Flags, Authoritative Mapping) + reconciles section names to canonical (Collaboration Defaults → Collaboration Stance). 7 total sections matching canonical structure. - workflow_policy.example.md — full reconcile to canonical 7-section structure (Standard Flow, Stage Definitions, Signal-over-Noise Rules, Risk and Autonomy Policy, Project Memory Contract, Parallelism Policy, Local Integration). Drops Bounded Automation / Cost Acknowledgment / Publication Boundary / Review Gate sections that were v1-era drift; cost-acknowledgment subsumed under Risk and Autonomy Policy. - agent_feedback.example.md — NEW file with canonical 3-section structure (How to classify + Universal rules + Universal-principled rules). Empty rule lists with format-only HTML-comment placeholders showing the expected entry shape (rule title / Rule / Why / How to apply). Content discipline: realistic-but-fictional placeholder values that demonstrate the FORMAT (e.g., planning_strictness:3 with explanatory note about what 3 means). Does NOT copy operator's actual personal content — no lived-behavior narratives, no axis values matching operator's elicited values, no personal anecdotes. Soak-protected surfaces touched: ZERO. Files are all under core/memory/global/examples/ (template tier; not core/hooks/* or kernel/*). No `episteme verify-examples` CLI in this Event (Component 5 deferred to a future Event).
|
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
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
Third v1.0.1 polish mini-batch CP shipped. Brings
core/memory/global/examples/to schema parity with the v2 canonicals so that fork-onboarding viaepisteme initseeds schema-faithful files instead of stale v1-era templates.Trigger. Events 65/66/71 privatized the maintainer's canonical profile content; the example templates that fork users seed via
episteme initwere left at their pre-v2-schema state. The four files in this PR were structurally / schema-wise inadequate to mimic the canonicals — the kernel hooks read canonical paths at runtime and fall back to defaults when axis data is missing, so fork users were getting generic-default kernel behavior instead of personalized-to-them behavior.What this changes
operator_profile.example.mdcognitive_profile.example.mdworkflow_policy.example.mdagent_feedback.example.mdoperator_profile.example.md(full v2 schema rewrite)Full v2 schema scaffolding: 16 axes with the per-axis metadata structure (
value/confidence/last_observed/evidence_refs/note).Each axis defaults to
confidence: stub(signals "fork user must elicit") with an inlinenotefield teaching the value range / enum + the kernel mechanism that consumes it (e.g., thepreferred_lens_orderderived knob readsdominant_lens; the Phase 12 audit floor readsasymmetry_posture).Includes the canonical's Legacy Working Style Summary section (kept for adapter compatibility) and the Review checklist for the operator (3-question discipline before flipping
stub→inferred→elicited).cognitive_profile.example.md(3 missing sections added; tone reconciled)Adds 3 sections that matched canonical structure but were absent from the prior template:
Renames
Collaboration Defaults→Collaboration Stanceto match canonical. Preserves the existing Foundational Mental Models section (Kahneman / Dalio / Boyd / Munger) which was the strongest part of the prior template.workflow_policy.example.md(structural reconcile to 7 canonical sections)Drops v1-era drift sections (Bounded Automation / Cost Acknowledgment / Publication Boundary / Review Gate); cost-acknowledgment subsumed under Risk and Autonomy Policy. New 7-section structure matches canonical:
episteme sync+episteme doctor)agent_feedback.example.md(NEW)Creates the missing template for fork users. 3-section canonical structure:
Triggering patternfield for pattern-gated rules.Empty rule lists are intentional — fork users accumulate rules from their own operator-agent interactions, not by inheriting the maintainer's. The format placeholders teach the rule shape without leaking maintainer content.
Content discipline
No operator-personal content leaked. Specifically excluded:
asymmetry_posturelived-behavior narrative (Events 65/66/67 references)What IS shared: the schema structure, the metadata format, the section taxonomy, the Foundational Mental Models commentary (Kahneman / Dalio / Boyd / Munger — these are public intellectual content already cited in
kernel/REFERENCES.md).Verification
operator_profile.example.mdenumerates all 16 v2 axes with validconfidence: stubdefaults../../../)episteme initin a fresh project + verifies seeded files match the templates exactly (manual post-merge)Soak-invariant
ZERO touches to
kernel/*/core/hooks/*/core/blueprints/*/src/episteme/*/tests/*/templates/*/labs/*. All edits undercore/memory/global/examples/(template tier).v1.0.1 polish queue post-Event-77
episteme profile audit ackCLI)episteme verify-examplesCLI; deferred)3 of 4 v1.0.1 polish CPs shipped. CP-AUDIT-ACK-01 is the largest remaining piece.
Cross-references
~/episteme-private/docs/cp-v1.0.1-polish.md§ CP-EXAMPLES-SCHEMA-PARITY-01kernel/OPERATOR_PROFILE_SCHEMA.md~/episteme-private/docs/PROGRESS.mdEvent 77 entry (private)