菜单
Bootstrap Sentrux architectural rules for harness projects — seed architecture.manifest.json, generate merge-safe .sentrux/rules.toml, and document bootstrap vs --force sync. Use during /harness-setup, when adding Sentrux to a repo, or when rules.toml is missing or out of date.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | harness-sentrux-setup |
| description | Bootstrap Sentrux architectural rules for harness projects — seed architecture.manifest.json, generate merge-safe .sentrux/rules.toml, and document bootstrap vs --force sync. Use during /harness-setup, when adding Sentrux to a repo, or when rules.toml is missing or out of date. |
/harness-setup Step 4.2 (Sentrux rules bootstrap).sentrux/rules.toml or harness-verify reports rules out of date.pi/harness/sentrux/architecture.manifest.json (layers, boundaries, constraints)| Role | Agent / command | Layer |
|---|---|---|
| Bootstrap | harness/sentrux-bootstrap, harness-sentrux-bootstrap.mjs | Greenfield seed + first sync |
| Steward | harness/sentrux-steward, /harness-sentrux-steward | Proposes manifest changes (artifacts/sentrux-manifest-proposal.yaml); chair applies |
| Sync | sentrux-rules-sync.mjs, /harness-sentrux-sync | Regenerates rules.toml from manifest after intent change |
| Observation | /harness-run, /harness-review | harness-sentrux-cli.mjs gate --save / check / gate → artifacts/sentrux-signal.yaml |
Never auto-sync manifest from directory trees. Material manifest edits need steward evidence + chair approval.
| Path | Role |
|---|---|
.pi/harness/sentrux/architecture.manifest.json | Source of truth (layers, boundaries, constraints) |
.sentrux/rules.toml | Generated Sentrux rules (commit to git) |
.sentrux/.harness-rules-meta.json | Sync metadata (gitignored) |
Custom TOML outside # --- harness:managed:start/end --- is preserved on every sync.
UP_PKG via .pi/scripts/README.md)| Situation | Command |
|---|---|
| First-time / harness-setup (idempotent) | node "$UP_PKG/.pi/scripts/harness-sentrux-bootstrap.mjs" |
| After manifest edits | node "$UP_PKG/.pi/scripts/harness-sentrux-bootstrap.mjs" --force |
| CI / verify only | node "$UP_PKG/.pi/scripts/sentrux-rules-sync.mjs" --check |
| Run/review Sentrux observation | node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check / gate [--save] |
| In pi session | /harness-sentrux-sync (extension; uses --force) |
Bootstrap vs --force: Default bootstrap/sync skips rewriting rules.toml when the manifest hash is unchanged. Use --force (or /harness-sentrux-sync) after changing architecture.manifest.json or when verify reports drift.
harness-setup Step 2.8 or harness-cli-verify.sh).UP_PKG):
node "$UP_PKG/.pi/scripts/harness-sentrux-bootstrap.mjs"
sentrux plugin add-standard (language plugins; harness-setup Step 2.8).node "$UP_PKG/.pi/scripts/harness-sentrux-cli.mjs" check — fix violations or tune manifest max_cc / layers..sentrux/rules.toml and project-specific architecture.manifest.json.harness-seed-project-contracts.mjs (Step 0.5) copies JSON schemas; bootstrap seeds the Sentrux manifest template when absent and sets project from package.json.
Do not copy ultimate-pi's layer paths blindly into unrelated layouts — edit manifest layers/boundaries for the target repo, then --force sync.
.pi/scripts/sentrux-rules-sync.mjs, harness-sentrux-bootstrap.mjs, harness-sentrux-cli.mjsharness/sentrux-bootstrap (setup), harness/sentrux-steward (intent proposals)sentrux-manifest-proposal.schema.json, sentrux-signal.schema.jsonCommit staged git changes with configurable message format and Co-authored-by trailer from .pi/auto-commit.json. Use when the user asks to commit, when /harness-auto or harness run completion requires a commit, or before any git commit — never use raw git commit -m.
Compile task-specific harness context using context-mode and graphify. Use for architecture questions, large codebase context before harness-plan or harness-run. NEVER use lean-ctx on harness paths.
Plan-phase Review Gate debate — pi-messenger threads, lane YAML, bus tools for parent orchestrator.
Structured user decisions via ask_user for harness setup, planning, and governance forks. Use with /harness-setup, /harness-plan, harness-auto plan phase, and when agents emit human_required.
Deprecated — use harness-review skill and /harness-review for the full post-run gate. This file remains as a pointer for older prompts.
Enforce harness governance phases, policy gates, budgets, and promotion rules. Use during execute, evaluate, merge, or when interpreting policy-gate / budget-guard messages.