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. Stateless: compile-time only, no execution-time state. Type: (ExecutionBlind, User, EVALUATE, ExecutionContext) → SituatedExecution. Alias: Prosoche(προσοχή).

AI & Automation 125 stars 11 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
70
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ₛ = ∅ → no_compile → deactivate -- nothing loop-consumable (relay) ∀b∈Bₛ: Compile(b) → κ ∨ ρ → (K, R) → Qc(K, R) → Stop → V → V = Adjust(d) → recompile(K, R, d) → (K, R) := (K', R') → Qc(K, R) V = Confirm → AcceptResiduals(R) → Emit(K)[TaskCreate...

Details

Author
jongwony
Repository
jongwony/epistemic-protocols
Created
7 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

Code & Development Solid

contextualize

Detect application-context mismatch after execution. Verifies applicability when correct output may not fit the actual context, registering each mismatch through a fail-closed deficit-fit certificate before adaptation, producing contextualized execution. The transformative revalidation loop is non-monotone — adapting the result mutates the evaluation target and can breed emergent mismatches; re-scan is mandatory. This is the non-monotone/transformative side of the contextualize ↔ distill boundary (distill is the claim-preserving side: it may add resolution or excise released bookkeeping in place, but never mutates what the record asserts). Type: (ApplicationDecontextualized, AI, CONTEXTUALIZE, Result) → ContextualizedExecution. Alias: Epharmoge(ἐφαρμογή).

125 Updated today
jongwony
AI & Automation Listed

byproxy

Contract-driven guard layer for coding tasks. Haiku explorers map terrain and fetch facts; the orchestrator surgically reads the critical path, authors falsifiable contracts, and directs — a thinker, not a doer, writing no code itself; a tool-less critic red-teams the contract; a Sonnet builder executes all implementation (tests, code, and the subtle fixes) under the orchestrator's terse direction; a cold same-tier auditor judges the result. Use whenever the user invokes byproxy, asks for a guarded/contracted/audited build, mentions explorers or design gates, or hands over a task where independent verification matters more than speed.

1 Updated 4 days ago
joaomdsg
AI & Automation Listed

operational-rigor

Core execution discipline for any non-trivial task — multi-step work, anything that modifies files or systems, debugging, or work whose correctness matters, even when the user does not ask for rigor. 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. Governs the task contract, action gating, scope containment, verification by execution, adversarial self-review, and honest completion claims. Do NOT load for single-step questions, pure explanation, or trivial edits; for delegating to subagents or reviewing agent output, also load delegation-and-review.

2 Updated yesterday
F-e-u-e-r