attend

Solid

Compile execution guardrails before autonomous execution. Infers a boundary map from context, partitions risks by velocity, compiles slow/threshold risks into verifiable predicates, and emits coarse goal entries for a downstream completion-predicate enforcer; fast risks are declared out of scope for harness-level gating; a loop-type interval lacking a termination predicate is confirmed before it proceeds unguarded. Stateless: compile-time only, no execution-time state. Type: (ExecutionBlind, User, EVALUATE, ExecutionContext) → SituatedExecution. Alias: Prosoche(προσοχή).

AI & Automation 163 stars 15 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
74
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Prosoche Protocol Compile execution guardrails before autonomous execution: infer a boundary map from context, partition risks by velocity, compile slow/threshold risks into verifiable conditions, and emit coarse goal entries that a downstream completion-predicate enforcer consumes. Type: `(ExecutionBlind, User, EVALUATE, ExecutionContext) → SituatedExecution`. ## Definition **Prosoche** (προσοχή): A dialogical act of sustained attention to execution risk — from the Stoic practice of self-aware engagement — resolving execution blindness at compile time. Before an autonomous execution interval begins, Prosoche infers the boundary signals the work is subject to, keeps only those whose violation is evaluable when the loop stops (slow/threshold risks), compiles each into a verifiable predicate, and hands the compiled set off as coarse goal entries. The attention is inscribed into the conditions; the protocol holds no state during execution. ``` ── FLOW ── Prosoche(C) → Infer(C) → B → Normalize(B) → B̂ → -- split signals decomposed (Slow part, Fast part) Partition(B̂) → (Bₛ, Bₓ) → Bₓ ≠ ∅ → OOS(Bₓ) -- fast risks declared out of scope (relay) Bₛ = ∅ ∧ loop_interval(C) → Qt(∅) → Stop → Vₜ -- empty guardrail set before a loop interval gates first (Vₜ arms below) Bₛ = ∅ → no_compile → deactivate -- otherwise: nothing loop-consumable; absent termination coverage named (relay) ∀b∈Bₛ: Compile(b) →...

Details

Author
jongwony
Repository
jongwony/epistemic-protocols
Created
9 months ago
Last Updated
today
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

governed-autonomy-loop

Turn any work-queue + any enforcement pipeline into a self-driving, self-healing, human-minimal autonomy loop with a control-systems safety envelope. A prose-defined governor closes a feedback loop over the queue, drives isolated worktree arcs to Done, is metacognitive (defers when the runtime can't support the act, escalates only when genuinely blocked, self-heals when the block clears), and NEVER performs the irreversible act itself — it delegates every merge/deploy/publish to an isolated arc gated by adversarial review + a policy gate + a server-side aggregate check. The controller is a markdown prompt interpreted fresh each tick; a thin tested shell (tick.sh) only schedules, locks, and logs. The skill SCAFFOLDS + GOVERNS a new loop instance: the invariant spine stays fixed, four adapters (tracker / irreversible-act + enforcement / runtime / partition) are per-instance, the deterministic core (scheduler, in-flight fold, reseed gate, config + denylist validation) is extracted into tested scripts, and the la

4 Updated yesterday
broomva
AI & Automation Solid

compound-v

Use when superpowers:brainstorming is about to begin (pre-brainstorm recon), OR has produced a spec, OR when superpowers:writing-plans has produced a plan, OR when about to invoke superpowers:subagent-driven-development or superpowers:executing-plans. Sidekick that intercepts these four Superpowers transitions — runs gated recon, triple parallel pre-flight, then materializes a manifest and dispatches the orchestrated, scope-enforced, resumable execution pipeline.

38 Updated yesterday
procoders
AI & Automation Listed

operational-rigor

The execution discipline for any non-trivial task — task contract before work, action gates before irreversible steps, scope control during, verification by execution, adversarial self-review, and honest completion reporting. Use at the START of any implementation/fix/refactor/automation task; BEFORE claiming anything is done, fixed, working, or complete; BEFORE any push, deploy, delete, send, purchase, or state-changing MCP call; when a task balloons or retries keep failing; and whenever you are about to report results to the user. The latest load moment is observable — you are about to take your first mutating action (edit, write, state-changing command); loading earlier is better, and if you notice you are already past it, load now. If in doubt whether this applies, it applies.

0 Updated today
firaen22