attend
SolidCompile 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(προσοχή).
Install
Quality Score: 81/100
Skill Content
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
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(ἐφαρμογή).
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.
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.