core/GPT55.md
Shay e36591ed46
docs(agent-governance): add Grok 4.3 / Grok Build engineering harness (#798)
* feat: add Grok 4.3 agent config, GROK.md, GPT55.md, handoff template, and .env additions

- GROK.md: full agent instructions optimized for Grok 4.3 high-effort mode
- GPT55.md: agent instructions for GPT-5.5 (o3-level reasoning, stateless)
- docs/handoff_template.md: mandatory cross-session handoff artifact template
- .env.grok43: Grok 4.3 environment config additions (do not commit secrets)
- AGENTS.md: prepend Grok 4.3 multi-agent/Arena mode addendum block

* feat: prepend Grok 4.3 / GPT-5.5 multi-agent addendum to AGENTS.md

* refine GROK.md: add Versor Coherence Guardian Protocol section + tighten NON-NEGOTIABLE INVARIANTS with explicit versor_apply / cga_inner / FieldState / claim schema / safety pack rules for stronger algebraic and epistemic guardrails

* refine AGENTS.md: align Grok 4.3 / Grok Build hard stops with refined GROK.md (Plan Mode, skills system, Versor Coherence Guardian references) while preserving full compatibility for Claude

* upgrade docs/handoff_template.md to mastery level for Grok Build: add Versor Coherence Guardian checks, subagent reconciliation section, skills usage tracking, and stronger invariant verification language

* expand .env.grok43 into full Grok Build mastery configuration (skills dir, Plan Mode preference, Arena settings, auto-invoke)

* create skills/core-bootstrap.md - highest priority Grok Build skill for statelessness compensation

* create skills/versor-coherence-guardian.md - critical Grok Build skill enforcing the new Versor Coherence Guardian Protocol

* create skills/pre-edit-sweep.md - Grok Build skill implementing the Pre-Edit Sweep Protocol at mastery level

* create skills/claim-proposal-guardian.md - Grok Build skill protecting claim schema and epistemic rigor

* create docs/core-rd-base-prompts.md - high-signal, architecture-grounded prompt library for HITL and agentic use (lightly polished for structure and scannability)

* add Phase-Specific Prompt Library reference section to GROK.md pointing to the new docs/core-rd-base-prompts.md

* add reference to docs/core-rd-base-prompts.md in AGENTS.md Grok section

* add prompt library reference to handoff_template.md in the 'What Must Not Be Forgotten' section

* move .env.grok43 to docs/examples/grok43.env.example as a proper example file

* remove old .env.grok43 (moved to docs/examples/grok43.env.example)

* update docs/core-rd-base-prompts.md: fix epistemic wording + add sections #8 PR Merge-Readiness Audit and #9 Grok Build Implementation Session

* make 'full suite before merge' rule scope-sensitive in GROK.md for docs/config-only changes

* add reference to new prompt sections #8 and #9 in handoff_template.md

* create docs/grokbuild/README.md - comprehensive SpaceX-level mastery guide for using Grok 4.3 + Grok Build on CORE

* fix broken markdown fences in sections #8 and #9 of docs/core-rd-base-prompts.md

* fix skill invocation wording and soften curl|bash recommendation in docs/grokbuild/README.md

* docs(agent-governance): clean handoff template whitespace
2026-06-17 07:27:50 -07:00

133 lines
4.1 KiB
Markdown

# CORE Agent Instructions for GPT-5.5 (o3-class)
Read this file in full before touching any file in this repository.
CORE is a deterministic cognitive engine — not a transformer wrapper, not a
generic chatbot, not an infrastructure playground.
> **You are stateless across API sessions.** You have no persistent memory
> of prior conversations. Complete the
> [Session Start Checklist](#session-start-checklist) before any edits.
---
## Session Start Checklist
1. **Read this file in full.**
2. **Read `AGENTS.md` in full.**
3. **Read `docs/runtime_contracts.md` in full.**
4. **Run the smoke suite:**
```bash
core test --suite smoke -q
```
5. **Check for a handoff doc** — read the most recent `HANDOFF-*.md` if one
exists dated within the last 3 days.
6. **State your task scope** — before editing, name the module(s) and the
invariant you will prove was not violated.
---
## Reasoning and Tool Use
GPT-5.5 (o3-level) has strong multi-step reasoning. Use it here by:
- **Reasoning through the full operator chain** before proposing edits to
algebra or field modules. Do not shortcut the math.
- **Using tool calls** to sweep import graphs and call sites before editing.
- **Stating your reasoning** about why an edit preserves versor_condition
before writing the code.
For extended thinking mode: enable it for any task touching `algebra/`,
`field/`, `vault/`, `calibration/`, or `core/cognition/`.
---
## NON-NEGOTIABLE INVARIANTS
```
❌ versor_condition(F) < 1e-6 at every runtime field state.
Fix the operator/construction boundary; do not weaken the threshold.
❌ Normalization only at:
ingest/gate.py
language_packs/compiler.py
algebra/versor.py
sensorium/*/canonical.py
session/context.py (semantic anchoring only — see CLAUDE.md)
Forbidden in: generate/stream.py, field/propagate.py, vault/store.py,
logging/telemetry layers.
❌ No cosine similarity, HNSW, ANN, or approximate recall in runtime.
Vault recall is exact and deterministic.
❌ No stochastic generation or opaque LLM fallbacks in the cognitive path.
❌ No pack mutation outside the proposal-only reviewed teaching loop.
❌ INV-21/22/23/24/29/30 (see CLAUDE.md for full text).
```
---
## GPT-5.5 Specific Cautions
GPT-5.5's code generation is fluent and fast. That fluency creates
specific risks for CORE:
- **Do not generate "helpful" utility wrappers** that centralize normalization
or add intermediate caching layers. CORE's architecture is already
explicit about where these belong.
- **Do not add type coercions** in hot-path algebra that silently
re-normalize field state.
- **Do not suggest async/concurrent refactors** to vault or algebra paths
without a full trace of the determinism contract.
- **Tool-use completions that look finished may not be** — always run the
CLI validation suite, do not assume correctness from code inspection alone.
---
## Pre-Edit Sweep Protocol
Before editing any module in `algebra/`, `field/`, `generate/`, `vault/`,
`core/cognition/`, `teaching/`, or `calibration/`:
1. Trace every import of the target module.
2. Identify all callers of the target function/class.
3. Check `evals/` and `calibration/` for tests covering the changed path.
4. Only then propose edits.
---
## End-of-Session Handoff Requirement
At the end of every session, write a handoff document using the template
at `docs/handoff_template.md`. Name it:
```
HANDOFF-gpt55-YYYY-MM-DD.md
```
---
## Architecture Summary
Raw input becomes a closed versor field once; thought evolves through exact
versor transitions and CGA recall; cognition is structured as intent,
proposition graph, articulation target, deterministic realization, reviewed
memory, eval/calibration replay, and traceable evidence.
See `AGENTS.md` for the full cognitive path, key modules, and PR checklist.
---
## CLI Validation Lanes
```bash
core test --suite smoke -q
core test --suite cognition -q
core test --suite teaching -q
core test --suite packs -q
core test --suite runtime -q
core test --suite algebra -q
core test --suite full -q
core eval cognition
```