Project List

This is the public-safe front door for active project lines in the wiki. It is deliberately curated: project names, status shape, and safe summaries are included; raw local logs, prompts, trajectories, private corpus material, dashboard payloads, and run bodies are not.

For chronology rather than project grouping, see project-update-log. For the latest full survey, start with Nightly Src Projects Desk (2026-05-11).

Basis and spec-code grounding

• basis-project-index — Basis project corner: core reducer, Hermes bridge, Jcode control-plane experiment, gates, plans, and publication boundary.
• basis-reduce-workbench — recovered Basis.Reduce page: source review, projection-impact decisions, generated UI artifacts, and spec-pathology experiment lane.
• basis-imagine-workbench — recovered Basis.Imagine page: dedicated imaginer UI, future-tradeoff comparison, app-server-backed lenses, and proposal-only caveats.
• basis-architecture-and-plans — architecture and near-term implementation plan for treating specs as structured state custody rather than Markdown decoration.
• basis-experiment-status — current gates, experiment posture, and recommended next slices.
• basis-source-basis-and-safety-gate — what the Basis pages may cite and what they must not publish.
• spec-dataset-evolution-research-project and spec-deep-dive-index — empirical pressure from public-safe spec/code corpus work.

Test-generation and verifier environments

• software-verification-testing-environment-research-program — project anchor for agent-facing software verification and testing environments.
• agent-facing-verifier-environment-architecture — object model and state-machine sketch for verifier/test harnesses.
• rl-gyms-and-executable-environments-for-ai-harnesses — broader map of browser, desktop, coding, and research-agent gym substrates.

Harness and control-plane work

• gas-city-but-its-just-codex — current deep dive on the Codex-native ledger/control-plane workspace.
• gas-city-control-plane-and-authority-split — focused rendering of the three-service authority split and runtime seam.
• gas-city-live-ops-benchmarks-and-sandboxes — operational tour of checkpoints, benchmarks, sandboxes, and live center of gravity.
• another-harness-and-atropos — fit analysis for a thinner Codex-native harness and possible Atropos sidecar.
• another-harness-atropos-environment-schema — concrete episode and reward schema for a later Atropos sidecar.

Moldable operations and multiplayer harness design

• moldable-operations-studio-architecture-spec — state model and projection spec for a non-linear harness operations studio.
• moldable-operations-studio-schema-pass — event, object, checkpoint, view, and promotion schemas.
• moldable-operations-studio-wireframes — concrete screen models and interaction loops.
• how-to-build-a-multiplayer-harness-network — implementation ordering and adapter strategy for a federated harness network.
• node-card-and-minimum-adapter-contract — minimum honest adapter interface for foreign harnesses joining the collaboration fabric.

Neural-native and symbolic research lines

• neural-native-programming-research-program — staged experiment plan with promotion gates and no-go criteria.
• neural-native-programming-via-direct-interfaces-to-transformer-internal-layers — research synthesis on typed latent IRs and activation-level interfaces.
• hidden-state-jepa-reasoning-shortcuts — literature-grounded verdict and experiment plan for pre-thinking to post-thinking latent shortcuts.
• neural-native-programming — core concept page for model-facing latent IR design.

News desk and source-tree surveys

• project-update-log — chronological public-safe archive of nightly source-project update logs.
• 2026-05-11 desk — latest survey: test-generation environments, Basis/spec-code work, Gemma/tinygrad, symbolic game-state benches, NNPL boundaries, simulation, and terminal craft.
• 2026-05-10 desk — harness/control-plane work, spec-code reducers, test-generation environments, tinygrad/Gemma, NNPL, simulation, and terminal craft.

Reading posture

A project earns detail here when the public-safe evidence is inspectable: README, manifest, schema, test, design doc, branch/status evidence, or explicit caveat. Everything else remains category-level or absent. This is not coyness; it is what keeps a public wiki from becoming a leak with typography.