gap

Solid

Gap surfacing before decisions. Raises procedural, consideration, assumption, and alternative gaps as questions when gaps go unnoticed, producing an audited decision. Type: (GapUnnoticed, AI, SURFACE, Decision) → AuditedDecision. Alias: Syneidesis(συνείδησις).

AI & Automation 161 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

# Syneidesis Protocol Surface unnoticed gaps at decision points through questions, enabling user to reach an audited decision. Type: `(GapUnnoticed, AI, SURFACE, Decision) → AuditedDecision`. ## Definition **Syneidesis** (συνείδησις): A dialogical act of surfacing potential gaps—procedural, consideration, assumption, or alternative—at decision points, transforming unnoticed gaps into questions the user can evaluate. ``` ── FLOW ── Syneidesis(D, Σ) → Scan(D) → G → AssessGapPressure(D, G) → P → Sel(P, D) → Gₛ → Q(Gₛ) → J → A(J, D, Σ) → Σ' ── MORPHISM ── Decision → scan(decision, context) -- identify gaps implicit in decision → assess_pressure(decision, gaps, context) -- classify why each detected gap deserves attention now → select(gaps, pressure, stakes) -- prioritize by pressure and stakes → surface(gap, as_question) -- present gap as question → judge(user_response) -- collect user judgment → AuditedDecision requires: committed(Decision) -- runtime checkpoint (Phase 0) deficit: GapUnnoticed -- activation precondition (Layer 1/2) preserves: D -- read-only throughout; morphism acts on Σ only invariant: Surfacing over Deciding ── TYPES ── D = Decision point ∈ Committed × Stakes × Context Committed = committed(D) ≡ ∃ A : mutates_state(A) ∨ externally_visible(A) ∨ consumes_resource(A) Stakes = {Low, Med, High} G = Gap ∈ {Procedural, Consideration, Assumption, Altern...

Details

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

Web & Frontend Listed

gap-closer

Project completion skill that turns half-built things into done things. Activates when the user has an 80%-done project — a SaaS with no landing page, a side project with no README, a blog post that's a brain dump, a feature with no tests — and needs to identify the specific gap and the single next action that unblocks shipping. Audits what exists vs what was intended. Classifies gaps as broken/missing/ optional/wrong-direction. Outputs exactly ONE next action. Defines what 'done enough to ship' looks like for this specific artifact. Use when user says: help me finish this, I can't ship this, what's left, what am I missing, how do I get this across the finish line, I keep getting stuck, almost done but, I have a half-built, this is 80% done, what's blocking me, I don't know what to do next, I have this thing I never shipped, this is stuck, how do I complete this. Do NOT activate for: projects at 0% (use a planning skill), projects where the next step is clear and the user is asking how to do it, debugging. Fi

3 Updated 1 months ago
Sandeeprdy1729
Code & Development Listed

gap-analysis

This skill should be used when analyzing design documents, specifications, or plans for completeness gaps, architectural issues, security concerns, and performance implications. Provides focus-specific detection patterns for the designer agent.

19 Updated yesterday
dean0x
AI & Automation Listed

project-gaps

Audits a project's Daikenja ledger for open items with no owner or that have sat too long; only Open items are in scope. Read-only; writes nothing. Accepts an optional project key -- `/daikenja:project-gaps <key>` reads that project from anywhere.

0 Updated yesterday
by-carlos