Skip to content
THE DEVELOPMENT WIKIPROJECT I SPACE FANTASY · CO-OP FPS · ROGUELIKE

AI wiki inspection and documentation evidence

This update explains current spawning, evidence/search and ownership for designers and developers. For example, the search page starts with a player disappearing behind cover, then separates remembered facts, predictions, inspection and finite effort. Diagrams and two small user-started sequences explain order/timing; they are schematic illustrations, not gameplay captures or simulation proof.

Scope, route and ownership

Documentation route under repository AGENTS.md and the workflow task-routing/closure policy; lead is the sole writer. Runtime, tuning, scenes/prefabs, Unity operations and game tests/builds are excluded. Owned work is authored wiki pages, glossary/catalogue notes/navigation, six local SVGs, minimal CSS/JavaScript support, generator wording and regenerated exports. No dependencies, publishing or implementation milestones.

Risk is bounded wiki presentation and source interpretation, with no authority/evidence/acceptance policy changes. Independent read-only source/technical review covers spawning and its amendments; independent document/design review covers explanation, status, visuals and controls. Lead reconciles source/assets/accepted decisions rather than votes and applies Ponytail completeness/correctness/simplicity inspection before scoped commit.

Hypothesis: separating implemented behavior, accepted direction, current provisional values and checkpoint evidence makes the systems understandable without implying production promotion. Contradictions between captions/current assets, invented connected reports, exhaustive-search claims or superseded population caps would fail this goal.

Revision and preserved working state

Initial inspection: 2a40e43a7afdef4ef84070c8f270e49565df5f49, branch codex/enemy-ai-rebuild. Existing changes included three director assets; targeting/bolt/perception/positioning/navigation source; two firing test files; the parent AI plan; custom arrival asset/meta; spawn research/companion; unrelated weapon/ability research; and an exposed-platform fix record. None were written or staged by this task.

During read-only inspection another task created 80f7fa87e98eb30a124d9a568d33e9727bfa2d8e, committing five targeting/perception/navigation/bolt source files, two firing test files and the exposed-platform fix record. The wiki was reconciled against that revision plus the remaining dirty authoring/planning. The machine-readable inspection records this revision, inspection UTC, remaining outside-task dirty paths and SHA-256 values; linked-source hashes are retained there as well. Collector provenance and catalogue input hashes retain refresh identity. Raw copied source/evidence lives in ignored _sources/, refreshed by the established generator; these local copies include uncommitted design documents and are not a separately published source archive.

Relevant dirty authoring is intentional: S2/S3 exploration now reads 4.5 credits/s, five initial credits and six-second opportunities; boss add limit is 12, versus the S3 original proposal of six. Those are inspected user values, not new balance approval. Persistent's current 20-second retention, 45 m travel and cone/radial values are read from its definitions. The sandbox's older comparison text and older disabled-cover-probe prose are superseded by current assets for factual tuning.

Decision precedence and gameplay limits

The current brief, AI settings, targeted parent-plan M5B/M6/closure sections, spawn research and the companion's later accepted amendments were read with source/assets. The later finite saving and boss/child exception decisions replace earlier research proposals; historical records are preserved. Source implements trusted child ledger contracts, while actual splitting/local placement remains M13.

M5/M5B search and S2 arrivals/elite follow-up have their recorded scoped acceptance. S3 gameplay is pending. Debug grouping acceptance does not close S3; S4/M6-SPAWNING-READY, C1–C3 and production promotion remain open. The later firing checkpoint retains its unresolved cover-timing miss, partial native results and human/broader acceptance. This wiki does not turn that checkpoint into a fresh integrated pass.

Historical automated counts on the ownership page are attributed summaries, not newly reused verification of this working tree and not a merged pass total. Representative hardware, separate-network play and role/boss/coordination acceptance remain separate. No new gameplay evidence was collected.

Verification packet and stop condition

Use TESTING's documentation boundary and the Wiki entries in TEST_CATALOGUE. Commands: Refresh-Wiki.ps1, Test-Wiki.ps1, Build-Wiki.ps1, then loopback-only Preview-Wiki.ps1 -SkipBuild. Check provenance, links/anchors, navigation/search, SVG rendering, keyboard/animation controls, reduced motion and narrow layouts. Duration initially unknown; local static collection/build/browser latency dominates. Escalate only source drift, factual conflicts, broken exports or unavailable rendering; never launch Unity to repair documentation proof.

During authoring, concurrent uncommitted director peer/harness work also appeared outside this task. It is retained in collector identity and the inspection JSON's later-state list, but is not treated as completed S4 proof or authorization for this task to operate the game. Original outside-task hashes were rechecked before closure; unchanged relevant source/decision hashes keep the explanations compatible with their inspected identity.

Document review and checks

Independent Sol 6.1 Medium read-only source/technical/Ponytail and document/design reviews found no remaining material blockers after compact delta reconciliation. Corrections separated saving from placement lifetime, recorded the externally committed firing checkpoint, distinguished connected hearing from planned report transport and made diagrams keyboard-scrollable. The lead remains the only writer.

  • Refresh-Wiki.ps1: 91 catalogue entries regenerated through the established collector, with current input hashes/provenance and 195 explicitly linked local source copies. No generated catalogue was hand-edited.
  • Test-Wiki.ps1: 31 documentation tests passed, plus identity/freshness/local link and anchor checks. An initial assertion still expected retired-AI wording; its documentation assertion was updated while preserving passive authoring/resistance checks. No game test was changed by this task.
  • Build-Wiki.ps1: strict MkDocs build and built links/anchors/assets passed across 125 HTML pages. Existing informational notices about unlisted catalogue index pages and upstream future MkDocs releases are not dependency changes.
  • node Tools/Wiki/test_ai_explainers.cjs: both modes pass deterministic no-autoplay, timing, pause/resume/replay/end, hidden-tab and reduced-motion fallback checks. Built-in Node libraries only; no installation or game execution.
  • Browser: actual loopback page preview, search by typed spawning (15 matching documents, new spawning page first), anchor navigation, actual animation start/end, replay and keyboard Space pause/replay. All six SVGs rendered, visually inspected, with no text outside their rendered bounds. Narrow 390×844 pages retain local diagram scrolling, controls and tables without horizontal page overflow. Keyboard focus and ArrowRight scrolling work on diagram regions. A Material list rule overrode the first inspection-grid selector; the scoped selector was corrected for final rendering.

Preview initially failed because sandbox sockets were restricted; the authorized loopback server was relaunched with approved socket access and returned HTTP 200. Failed initial tabs were replaced; no browser security policy was bypassed. Source changes in the concurrent harness invalidated intermediate snapshots; only refreshed final checks are claimed. These interruptions supply no gameplay evidence.

Limits: this browser exposes no reduced-motion or JavaScript-disabled rendering override. Those fallback paths were checked through source/controlled DOM-clock fixtures and static HTML, not an actual reduced-motion/no-JavaScript browser capture. Native Unity diagnostic narrow-layout/human acceptance limits remain those of their gameplay records. No new gameplay, Editor, network, hardware or build-player checks were run.

Stop after final verification and a scoped local wiki commit, preserving all outside-task changes/staging. No push, amend, publishing or advancement of implementation milestones.

Search illustration revision — 16 October 2026

The user identified the combined search example as hard to understand and supplied a top-down L-wall/ray sketch as a conceptual reference, explicitly excluding its look and colours. The later user amendment removes inner cover and requests separate wall-hit and movement-prediction illustrations. This documentation-only follow-up uses the wiki's existing palette and two code-generated SVGs. Hypothesis: separating measured wall hits from far-side guesses, and real sight samples from frozen motion/radial guesses, makes prediction generation easier to understand. Viewpoint/inspection prose remains below.

Baseline: e11f4315c572e613aafa24adc91e74c3d19badc1, with the existing director authoring, AI/test harness/planning/research edits preserved. No runtime, tuning, Unity operation or game test/build is authorized or needed. Medium bounded documentation presentation; lead writes, independent Sol 6.1 Medium design review supplies pre/post inspection. Source constraints are the captured-eye/cone/ground/path rules in the existing planner and raw motion/radial hypothesis generation in the same planner. No policy or gameplay acceptance changes.

Owned files: paired assets/ai/search-predictions.svg / search-example.svg, their reproducible Tools/Wiki/generate_search_diagrams.py, perception-page text/alt captions, upkeep instructions and this record; refresh-generated identity files as required. Check schematic wall hits/miss, visible last sight, wall-free observed motion and movement/radial arithmetic using generator assertions; run refresh, Test-Wiki and Build-Wiki; render both SVGs and inspect the changed page at normal/narrow widths. Duration initially unknown. Escalate factual or readability contradictions; stop after document review, scoped local commit and verified update of the existing public Pages site. No other diagrams or implementation milestones are advanced.

Independent final source/design review cleared the corrected visible last sight, outer-L geometry, motion arithmetic and sixteen attempted radial locations. Its small clipping-wording correction was applied. The initial draft combined viewpoints and inner cover; neither remains in the amended pair. Two SVGs rendered with no out-of-bound text. Final integrated article checks confirm both new images load, the new section anchor appears in navigation, and 390×844 layout has no horizontal page overflow. Each diagram retains its keyboard-focusable local scrollbar; ArrowRight moves the focused movement diagram. Static SVGs add no animation or motion preference change.

Fresh generator assertions, Refresh-Wiki, all 31 Test-Wiki documentation tests and strict Build-Wiki with link/anchor/asset validation across 125 HTML pages passed. No game code, tuning, Unity or game checks changed. Existing animation verification is unchanged historical evidence from the original wiki packet; this follow-up makes no new reduced-motion browser claim. No pending gameplay acceptance is closed.