Summary
Define the conditions under which standard endeavor procedures (plan → design → implement → review) can be bypassed for urgent or low-risk changes, and what the bypassed procedure looks like.
Motivation
The emsemioverse endeavor has a growing body of method: plans document work before it begins, decision records capture architectural choices, skills codify recurring operations, and policies constrain behavior. This method exists to prevent waste, ensure traceability, and enable resumption across sessions.
But some changes are urgent or trivially correct and the full procedure
adds friction without proportional value. The enrichment provenance
change to infer-triage-frontmatter.py (2026-03-08) was an example:
the change was well-understood, low-risk, immediately needed, and
the act of planning it would have taken longer than doing it.
The endeavor currently has no documented way to say “this change bypasses the standard process” and no record of what was bypassed or why. The change just happens, and the method-practice gap grows silently.
This plan addresses the meta-problem: when the standard process is itself the obstacle, how does the endeavor handle that without abandoning traceability?
Star Trek influence
The Starfleet model provides a useful analogy. Standard operations follow established procedures. But the captain can override procedures in emergencies — and the override is itself logged, with justification, and subject to later review. The override doesn’t abolish the procedure; it creates a documented exception that the procedure can learn from.
Key elements from this analogy:
- Override authority: who can bypass procedures (emsenn, not agents)
- Override logging: the bypass is recorded with justification
- Post-bypass review: did the bypass reveal a gap in the standard procedure? If so, update the procedure.
- Backup systems: redundancy means a bypass doesn’t create a single point of failure
Research phase
Existing practice
- The enrichment provenance change (2026-03-08) was done by bypassing the plan → implement cycle. The user said “immediately make these changes… bypassing standard endeavor procedures.”
- Small fixes (typos, broken links) are regularly made without plans.
- No record exists of which changes bypassed procedures or why.
Existing method
- Policy 008 (prompts become artifacts) says: “if the work is small enough to complete in a few minutes with no ambiguity, just do it.” This is the closest existing exception to the plan-first rule.
- The semiotic-PM specification defines cycles, milestones, and plans, but has no “expedited” or “emergency” category.
- The endeavor lifecycle in semiotic-endeavor has transition guards, but no “fast-track” transitions.
Steps
-
Define the bypass taxonomy: categorize the kinds of procedure bypasses that occur. At minimum: trivial fix (typo, broken link), urgent change (blocking other work), user-directed override (emsenn says “just do it”).
-
Define the bypass record format: what metadata captures a bypass? At minimum: what was bypassed, why, by whose authority, and what the outcome was. This could be a commit message convention, a frontmatter field, or a lightweight record.
-
Define the post-bypass review: after a bypass, what happens? At minimum: the next assessment should note the bypass and evaluate whether the standard procedure needs updating.
-
Integrate with semiotic-PM: add an “expedited” plan type or a “bypass” tag to the planning vocabulary.
-
Integrate with policy 008: refine the “just do it” threshold to be more precise about when full planning is required vs. when a bypass record suffices.
Done when
- A taxonomy of bypass types exists
- A bypass record format is specified
- The post-bypass review procedure is documented
- Policy 008 is refined to reference the bypass procedure
Dependencies
Independent. The specification should be written before the next assessment so that future bypasses can be tracked.
Log
2026-03-08 — Created from emsenn’s observation during the enrichment provenance change: “bypassing standard endeavor procedures… which is itself something that needs to be planned out as a set of procedures!” The Star Trek/Starfleet influence was cited as inspiration for how overrides should work: logged, justified, and subject to review.