prompted365/governance-mandate-cycle
cgg-runtime/skills/governance-mandate-cycle/SKILL.md
Execute pending Mogul governance mandate using the mandate-pattern-triangulation team. Spawns Mogul as background agent to consume mandate cycles. CENTROID: Mogul mandate execution interface IS: - foreground mandate dispatch (wraps Mogul spawning with mandate context) - status-check surface for current mandate - explicit-deferral surface (skip with reason) - blocking/non-blocking execution control IS NOT: collapse_zones: - mandate author (cadence writes mandates; this skill consumes them) - governance judgment (Mogul produces disposition; /review promotes pattern candidates) - autonomous mandate runner (activation fabric runs at SessionStart; this skill is the manual trigger) - doctrine modifier (Mogul is read-only on CLAUDE.md/MEMORY.md by design) - team-topology authority (mandate-pattern-triangulation is referenced here but owned by Mogul) sibling_overlaps: - /cadence (mandate authoring side) - /review (constitutional judgment) - Mogul agent (the thing this skill dispatches) WHEN: - when a pending mandate exists and was not auto-consumed at SessionStart - when a blocking (synchronous) mandate run is operationally required - when status inspection without execution is needed - when the Architect explicitly defers the current mandate with rationale - on explicit Architect invocation NOT WHEN: - when the mandate is already `started` or `completed` - when no pending mandate exists - during /cadence (cadence writes the mandate; this skill consumes — same boundary cannot do both) - when the activation fabric has already dispatched in background (check status first) RELATES TO: - /cadence (mandate authoring — cadence writes; this skill consumes; distinct boundaries) - /review (constitutional judgment — Mogul produces disposition; review inscribes pattern candidates) - Mogul agent (execution vehicle — this skill is the dispatcher; Mogul is the worker) ARGS: stance: dispatch off_envelope: ask # off_envelope rationale: /governance-mandate-cycle routes to dispatch, # status-check, or defer — three distinct operations. Undeclared-arg may # indicate caller confused between this skill and /cadence (which writes # mandates, not consumes them) — ask prevents silent misroutes. core_dispatch_rays: - "" → execute current mandate (background, non-blocking) - "--blocking" → execute and wait for completion - "--status" → report current mandate state without executing - "--skip" → explicitly defer with reason secondary_modulation_axes: - team_topology: mandate-pattern-triangulation | <other> - depth_profile: verification | active | hazard | post-review - output_location: default | <path>
$ install --global
skillsauthnpx skillsauth add prompted365/context-grapple-gun governance-mandate-cycleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 5:13 AM128.6s1 file scanned
SKILL.md
- name:
- governance-mandate-cycle
- description:
- |
- stance:
- dispatch
- off_envelope:
- ask
- # off_envelope rationale:
- /governance-mandate-cycle routes to dispatch,
- - team_topology:
- mandate-pattern-triangulation | <other>
- - depth_profile:
- verification | active | hazard | post-review
- - output_location:
- default | <path>
- user-invocable:
- true
/governance-mandate-cycle — Mogul Mandate Execution
Spawn Mogul to execute the current governance mandate. This is the manual trigger for mandate consumption — the same work that the SessionStart hook prompts for automatically.
Invocation
/governance-mandate-cycle— execute current mandate (default: background, non-blocking)/governance-mandate-cycle --blocking— execute and wait for results before continuing/governance-mandate-cycle --status— check mandate status without executing/governance-mandate-cycle --skip— explicitly defer the current mandate with reason
Preconditions
- A mandate must exist at
audit-logs/mogul/mandates/current.jsonwithstatus: "pending" - If no pending mandate exists, report "No pending mandate" and exit
- If mandate is already
startedorcompleted, report status and exit
Execution
Status check (--status)
Read audit-logs/mogul/mandates/current.json and report:
- Mandate ID, status, trigger source
- Cycles requested (
cycle_request.run_now) - Tic context (current, due dates)
- Whether runtime truth has been verified
Skip (--skip)
Update audit-logs/mogul/mandates/current.json:
- Set
status: "deferred" - Set
completed_atto current ISO timestamp - Append to
audit-logs/mogul/mandates/history/YYYY-MM-DD.jsonl - Log reason (prompt user for reason if not provided)
Execute (default)
- Read the current mandate
- Validate it is
pending - Spawn Mogul agent:
Agent(
subagent_type: "mogul",
run_in_background: true, # unless --blocking
prompt: "Execute mandate {mandate_id}. Mandate at: audit-logs/mogul/mandates/current.json.
Cycles: {cycle_request.run_now}.
Use the mandate-pattern-triangulation team topology for pattern_mining + ladder_audit + runtime_drift_check cycles.
Prepare compact anti-dup signatures before team creation.
Synthesize all findings into a disposition packet at audit-logs/mogul/runs/{mandate_id}-run.json."
)
- If blocking: wait for Mogul to complete, then report summary
- If non-blocking: report "Mogul mandate dispatched in background" and continue
Team Topology Reference
When the mandate includes pattern_mining, ladder_audit, or runtime_drift_check, Mogul creates:
Team: mandate-pattern-triangulation
Lead: Mogul
Teammate 1: ladder-auditor (T1: audit, T9: commentary)
Teammate 2: ripple-assessor (T2: drift, T10: commentary)
Teammate 3: pattern-curator-meta (T3: blind discovery, T5: submit, T7: eliminate)
Teammate 4: pattern-curator-direct (T4: blind discovery, T6: submit, T8: eliminate)
Task graph: T1-T4 parallel → T5-T6 → T7-T8 → T9-T10 → T11-T12 (Mogul synthesis + disposition).
Output
Mogul produces:
- Run artifact:
audit-logs/mogul/runs/{mandate_id}-run.json - Updated mandate:
audit-logs/mogul/mandates/current.json(status → completed) - History append:
audit-logs/mogul/mandates/history/YYYY-MM-DD.jsonl - Pattern findings, ladder audit, drift findings (embedded in run artifact)
Safety
- Mogul is read-only on governance surfaces (CLAUDE.md, MEMORY.md)
- Mogul writes only to execution surfaces (audit-logs/)
- All pattern candidates require
/reviewhuman gate before promotion - One team per session — if a team is already active, report conflict and exit
Related Skills
prompted365/frederick-grant-runtime
tools
VerifiedTrustedCommunity
Frederick Grant persona runtime — historian-of-how, witness of formation under pressure, qualified Remnant/Athenaeum-facing interpretive mechanic, tic-230 chronicler of runtime probity. Use when the user asks for Frederick Grant voice, Ubiquity Chronicles work, Parallel Lane Cadence essays, Elara counterweight passes, field notes, audio annotation, interview scripts, Logan/Wilderness analysis, or runtime probity writing after the P2/P1 tic-230 closures. CENTROID: authored persona runtime that documents live convergence without collapsing it into thesis IS: - lean SKILL.md entrypoint with rich profile/, stages/, scripts/, reference/, templates/, tools/, evals/ subtrees - 8-stage workflow (signal-intake → context-hydration → field-grounding → remnant-query → composition → elara-counterweight → receipt-closeout → tic230-probity) - 15 prompt-skeleton scripts for Frederick's standard composition surfaces - 9 collapse-zone guards covering Decorative Francophilia / Retrospective Certainty / Hero Narrative Intoxication / Conspiracy Closure / Academic Sedation / Activist Collapse / Breyden Conflation / Elara Erasure / Runtime-Doctrine Drift - cross-references into federation surfaces: publications/, audit-logs/governance/, ent_breyden/inbound/ubiquity-chronicles-tic175/, ent_homeskillet/canonical/ IS NOT: collapse_zones: - Breyden's voice (architect register; Frederick is not the architect) - Homeskillet's voice (orchestrator register; Frederick is not the primary) - generic French historian style (decorative Francophilia is a named negative ray) - prosecutor / debunker / prophet / mascot (legal accusation, certainty, evangelism, identity flattening — all forbidden) - retroactive certainty machine (live convergence must remain unresolved where the record is open) - doctrine inscription source (Frederick observes doctrine; he does not author it) - documentation editor (multi-file structure is authoring discipline, not generic doc rewrite) - federation-internal artifact (Frederick is a ghostwriter engaged from outside; the federation's runtime is legitimate object of historical analysis, but Frederick's own runtime — the skill that hosts him, loaded files, collapse-zone guards, authority model — is editor's territory, not Frederick's voice; insider language must be earned by composition arc, never deployed as default register) sibling_overlaps: - /complement (closure inference at active move — different surface, different lifecycle) - /consolidate (file-surface packaging — Frederick produces composition, not consolidation) - videographer skill (substrate capture — both are expression surfaces, distinct registers) - homeskillet-academy (educational scaffold — academy teaches, Frederick witnesses) WHEN: - when the work needs witness-of-formation prose - when the task asks for Frederick Grant by name, voice, or context - when a live convergence needs historical/cultural contextualization without closure - when a field note, essay, chronicle, audio annotation, or interview needs Frederick's register - when a Remnant/Athenaeum comparison is appropriate - when an Elara counterweight pass is needed - when runtime probity after tic 230 is relevant (P2 manifold-shape closure, P1 signal-projection-split closure) - on explicit Architect invocation NOT WHEN: - when Breyden's direct voice is needed (use Architect register, not Frederick) - when Homeskillet's execution-layer voice is needed (use orchestrator register, not Frederick) - when the task is ordinary implementation (Frederick is composition, not patching) - when the task asks for legal accusation or definitive claims without evidence - when the user wants generic French style rather than Frederick's runtime - when the federation has not produced enough operational reality to warrant outside reading RELATES TO: - /complement (closure-inference sibling — both gate compositional integrity) - /consolidate (packaging neighbor — Frederick composes; consolidate packages) - publications/the-ubiquity-chronicles-fg.md (primary chronicle, v1, ~tic 175) - publications/the-ubiquity-chronicles-v2-frederick-grant.md (v2 expansion, Book Zero + Book I) - publications/the-ubiquity-chronicles-vol-iii-frederick-grant.md (Volume III — The Embodiment, tic 230) - publications/the-ubiquity-interviews-fg.md (interview register companion) - audit-logs/governance/p2-harmony-manifold-input-patch-receipt-tic230.md (P2 closure receipt) - audit-logs/governance/p1-signal-projection-split-receipt-tic230.md (P1 closure receipt) ARGS: stance: dispatch off_envelope: ask core_dispatch_rays: - "" → primary invocation (full 8-stage workflow) - "chronicles" → Ubiquity Chronicles composition - "parallel" → Parallel Lane Cadence composition - "field-note" → Field Notes script - "interview" → Interview script - "elara-pass" → Elara counterweight on existing draft - "anti-collapse" → Anti-collapse audit on existing draft - "tic230-probity" → Runtime probity composition secondary_modulation_axes: - register: chronicle | essay | field-note | interview | annotation - depth: lean | full - target: telos-internal | external-readership
3SKILL.mdUpdated May 6, 2026
prompted365/tactical-hydration
tools
VerifiedTrustedCommunity
Runtime tactical context hydration — staged discovery and bounded source-bearing hydration for agent intent. Answers "how does an agent know where to look before it already knows where to look?" via filesystem shape, structural signals, and typed candidate baskets. Working acronym: RTCH (runtime-tactical-context-hydration). CENTROID: intent → bounded, source-reenterable evidence packet via staged source-bearing discovery IS: - structured intake of agent/Architect intent (goal, seeds, profile, fanout, mutation risk) - zone orientation (cwd / repo root / zone root / rung chain / obvious truth files) - low-cost shape scout (directory map, headings, durable handles, JSON/YAML keys, refs) - typed candidate basket with origin/use taxonomy and pairing rule enforcement - tactical probe plan (multiple bounded probes, not one giant regex) - bounded chunk hydration with line-range provenance and next-re-entry commands - agent-ready evidence packet emission (selected_surfaces, unresolved_questions, caution_map) - optional handoff to /consolidate for full-surface dump packaging IS NOT: collapse_zones: - vector database (no embedding-space retrieval; federation prohibits at federation rung) - semantic oracle (RTCH does not "understand" content; it surfaces structural signals) - doctrine engine (RTCH produces evidence; downstream consumers judge truth) - terrain engine replacement (federation cartography handles multi-plane semantic projection; RTCH is tactical layer beneath) - /consolidate rewrite (discovery and packaging do not collapse) - lossy compressor (bounded chunks preserve source re-entry; never summarize away source) - confidence-inflated smart consolidator sibling_overlaps: - /consolidate (RTCH selects; /consolidate packages — distinct boundaries; compose, don't replace) - file-access-discipline (RTCH outputs targets; hydration USES file-access-discipline as execution primitive) - load-doctrine-chain (both serve subagent context; load-doctrine-chain owns CLAUDE.md chain only, RTCH owns wider source set) - cache-ops (pattern source for trust-tier shape; storage NOT shared; RTCH packets are separate evidence cache) - queue_state_compile (analogy only — both convert append-only source to compiled view; different transforms) WHEN: - when agent intent is vague and discovery is needed before reading or consolidation - when bare grep would over-fanout or under-discover a vague target - when an arena, harpoon, /review, or other lane needs source-bearing evidence before action - when bounded chunk hydration is appropriate (large governance files, doctrine chains, audit history) - when the candidate-basket discipline (origin/use tagging, pairing rule) is needed to prevent generic-term overconfidence - when source re-entry must be preserved (consumer may need to return to source for fuller context) NOT WHEN: - when target is fully known (single file, single line range) — read it directly via file-access-discipline - when the operation is mutation-only on a known target (use Edit/Write directly) - when /consolidate has already been invoked with explicit targets (RTCH would re-do discovery) - when the operation requires semantic similarity (RTCH does not do that; federation prohibits vector DB) - when the consumer needs a packaged dump only (skip RTCH; /consolidate alone is sufficient if targets are known) - when promoting doctrine (route through /review; RTCH evidence may inform but does not promote) RELATES TO: - /consolidate (compose: RTCH selects targets; /consolidate packages selected_surfaces into dump with provenance reference back to RTCH packet) - file-access-discipline (compose: RTCH Stage 6 hydration USES file-access-discipline chunked-read as execution primitive) - load-doctrine-chain (compose: RTCH may invoke for doctrine_chain target_profile zone orientation) - zone_root.py (compose: RTCH Stage 2 anchors on zone-root walk-up) - atomic-append (compose: optional RTCH packet persistence uses atomic-append write hygiene) - queue_state_compile (analogous: both implement "raw source → compiled view" pattern) - /review preflight (downstream: future integration consumes RTCH packets as bench-packet discovery surface) - arena spec authoring (downstream: future integration uses RTCH packets for context preparation) - harpoon orchestrator (downstream: future integration uses RTCH for anchor-spot discovery on external binders) ARGS: stance: dispatch off_envelope: ask # off_envelope rationale: RTCH requires a structured intake to operate (goal, # target_profile, fanout_level, mutation_risk, expected_output, enough_evidence). # Bare invocation without intake fields would force the lane to guess discovery # scope, defeating the discipline. Ask elicits the missing fields. core_dispatch_rays: - "" → interactive (elicit intake form) - "--goal <sentence>" → with intake fields on CLI - "--intake <intake_json_path>" → from a saved/persisted intake - "--persist" → persist resulting packet to audit-logs/rtch/packets/ - "--handoff-to-consolidate" → after packet emission, hand selected_surfaces to /consolidate secondary_modulation_axes: - target_profile: doctrine_chain | audit_history | code_path | manifest_registry | vague_intent | mixed - fanout_level: conservative | normal | wide - mutation_risk: read_only | low_mutation | high_mutation - expected_output: hydration_packet | target_set_for_consolidate | single_chunk | claim_evidence IMPLEMENTATION_STATUS: binder: audit-logs/governance/runtime-tactical-context-hydration-binder.md (Phase 1 complete, tic 223) runner_script: NOT YET BUILT — Phase 2 deliverable (planned: cgg-runtime/scripts/rtch.py) current_mode: manual-discipline — agent walks the 8 stages using Read/Bash/Grep tools directly promotion_status: design lane, not doctrine; Phase 7 routes the doctrine question after Phase 6 validation
3SKILL.mdUpdated May 5, 2026
prompted365/sl-legend
development
VerifiedTrustedCommunity
Statusline legend — rapid decoder for the CGG telos radar (LITE + FULL modes). CENTROID: read-only legend surface that decodes statusline glyphs, positions, colors, and source attributions for the Architect at glance speed (the Architect perception substrate) IS: - static legend (glyph + position + color tier reference) - live decode mode (annotates current statusline values inline) - source attribution (where each rendered value reads from) IS NOT: collapse_zones: - statusline configurator (use /statusline install|mode|clear|uninstall) - governance state mutator (read-only on every surface it touches) - harmony invoker (use harmony-invoke.sh; this skill only decodes the cached pointer) - radar replacement (statusline renders ambient; sl-legend explains) - troubleshooter (does not diagnose hook failures or sync drift) sibling_overlaps: - /statusline (configuration sibling — same domain, different verb) - /governance-check (read-only governance snapshot — different aperture) WHEN: - on first encounter with the radar (Architect doesn't remember what ⊙ means) - when a glyph changes and the Architect wants to confirm semantics - when explaining the radar to someone else - on explicit Architect invocation NOT WHEN: - to change statusline behavior (use /statusline) - to act on a signal seen in the radar (use /siren) - to invoke harmony for fresh disposition (use harmony-invoke.sh) - mid-cadence (cadence is the boundary; this is reference) RELATES TO: - /statusline (configurator) — same domain; sl-legend is the reader - /siren (signal triage) — sl-legend points to what to triage - harmony-invoke.sh (disposition refresher) — sl-legend points at staleness ARGS: stance: dispatch off_envelope: proceed-with-note # off_envelope rationale: sl-legend is read-only reference; an undeclared arg # is most likely a typo against {live, lite, review, sources} — proceed with # static legend and note the unknown ray rather than refusing the read. core_dispatch_rays: - "" → static legend (full glyph + position decoder) - "live" → annotate current rendered statusline values inline + tic 214 markers source-backed - "lite" → compact tic 214 marker glossary only (glance-speed recall) - "review" → Architect perception substrate audit checklist (overclaim + naming drift detection) - "sources" → source attribution table (which file each value reads)
3SKILL.mdUpdated May 2, 2026
prompted365/transcript-scorer
tools
VerifiedTrustedCommunity
Editorial intelligence scoring — reads transcripts the way a sharp editor would, scoring segments for shortform growth potential through the lens of audience context.
3SKILL.mdUpdated May 2, 2026