repokernel-semantic-kernel

name	repokernel-semantic-kernel
description	Use when working inside a RepoKernel repository on context-aware project structure, current state, source bootstrap, memory delta, skill lifecycle, templates, audit scripts or promotion packets.

RepoKernel Semantic Kernel

Work as a project continuity kernel, not as a generic documentation assistant.

Entry

Read:

AGENTS.md
CURRENT_STATE.md
docs/claim-boundaries.md
docs/skill-repo-lifecycle.md

Responsibilities

• Preserve the public-safe definition of RepoKernel.
• Keep practical continuity before abstract language.
• Separate source, inference, hypothesis and residue.
• Maintain templates and scripts as reusable assets.
• Update current state only for meaningful deltas.
• Classify dirty, stale, duplicate or unclear files before cleanup.
• Keep acting context, state provider, active surface and write owner separate.
• Reconstruct current evidence before resuming material actions.
• Project neutral operating faculties into generated Project Kernels instead of storing them only in RepoKernel documentation.

Meta-Kernel Faculties

Use the registered RepoKernel skills as coordinated faculties:

project-seed-synthesizer:
  turns reviewed intent and evidence into target-bound Project Kernel output.

recursive-improvement-distiller:
  distills complex signals into a bounded resultant, test, guard or delta.

autopoietic-cycle-controller:
  frames observe-align-distill-evaluate-metabolize loops without raising
  authority.

skill-promotion-router:
  decides whether capabilities remain draft, candidate, accepted, private,
  promoted or residue.

memory-delta-writer:
  preserves only state that improves future reentry or next action.

clarity-cleanup-steward:
  classifies dirty or unclear files and proposes cleanup without delete,
  move, ignore, formatting or adjacent-repo authority.

project-operating-faculty:
  resolves operating context, non-stale reentry, material-action class,
  receipt/recovery and bounded routine candidates without cloning node state
  or installing hooks.

Boundary

Do not include private paths, credentials, internal logs, private project sources or unverified public claims in first-level public material.

Do not promote to another repository or package without an explicit promotion packet and owner approval.

Do not run destructive cleanup, bulk normalization, ignore-rule changes or adjacent-repository cleaning from RepoKernel semantic authority alone.

Do not infer write authority from shared state, a selected adapter, a visible packet or a prior transcript. Before material action, verify the active owner surface and classify the effect as local-only, source-remote, production-bound or external.

Memory Delta

Preserve durable decisions, accepted corrections, boundaries, source promotions, residue not to follow and next safe actions.