Basis Source Basis and Safety Gate

Purpose

This page defines what the Basis wiki corner may cite, what it must not publish, and how future updates should avoid turning private run state into public prose.

It is the boring page. Boring pages are where systems remain housebroken.

Source basis

Claim scope	Source	Public-safe use	Hard limit
Core Basis architecture	/Users/ericfode/src/basis safe files and nightly-src-projects-desk-2026-05-10	commit state, tests, compile/format gate, safe file/module responsibilities	no raw provider streams or local run payloads
Basis.Reduce recovery	/Users/ericfode/.codex/worktrees/4e6b/basis, safe git metadata, tracked filenames, generated UI artifacts, and aggregate experiment JSON status	basis-reduce-workbench, branch/commit names, control-gate result, generated-image paths, aggregate score/status fields	no raw Codex JSONL bodies, prompt bodies, private packet bodies, or candidate implementation dumps
Basis.Imagine recovery	/Users/ericfode/.codex/worktrees/95ae/basis, safe git metadata, tracked/untracked filenames, generated UI artifacts, and syntax/test outcomes	basis-imagine-workbench, dirty-worktree summary, route names, future labels, proposal-only synthesis	no app-server turn bodies, live stream content, local dashboard state payloads, or unreviewed patches as accepted direction
Hermes plugin bridge	/Users/ericfode/src/basis-hermes safe files and repair note evidence	tool names, schema posture, tests, dashboard/API route names	no arbitrary local file contents or private dashboard outputs
Jcode reducer/control plane	/Users/ericfode/src/basis-jcode/components/spec-basis-reducer source/tests plus .basis counts	architecture, test status, run names/counts, dashboard loopback status	no .basis packet/log/prompt/NDJSON bodies
Spec corpus relation	spec-dataset-evolution-research-project and spec-deep-dive-index	aggregate counts, provenance policy, public-safe synthesis	no raw copied corpus specs
Publication policy	spec-deep-dive-wiki-ingest-project and safety-and-permissions	fail-closed public-safety rules	no secrets, PII, private prompts, evaluator payloads, or run bodies
Experiment discipline	evaluation-and-review-loops and work-management-primitives	gates, no-go criteria, status tables	no claim without verifier or caveat

Allowed public evidence

Allowed by default:

• repository names and local paths;
• branch/commit/status summaries;
• safe filenames and module responsibilities;
• test, compile, lint, and format outcomes;
• route/tool names;
• .basis directory names and aggregate counts;
• output filenames;
• recovered/generated UI images when explicitly labeled as artifacts rather than accepted runtime state;
• aggregate experiment status fields and scores when they do not expose raw evaluator cases, hidden oracles, or private candidate bodies;
• synthetic examples written specifically for publication;
• short architectural synthesis.

Allowed only after separate review:

• excerpts from public upstream source files;
• synthetic packet bodies;
• redacted run summaries;
• dashboard screenshots or exports.

Excluded evidence

Do not publish:

• .basis raw run trees;
• raw Codex JSONL session bodies;
• app-server turn bodies or model stream payloads;
• prompt text;
• NDJSON event bodies;
• stdout/stderr log bodies;
• worker packet bodies;
• validation bodies from real private runs;
• local dashboard /api/state payloads;
• local service configuration;
• private corpus raw files;
• evaluator-like payloads;
• hidden references/oracles;
• credentials, tokens, .env contents, or secret-adjacent values;
• raw model outputs that have not been explicitly accepted and reviewed.

Public update checklist

Before adding a Basis wiki update:

1. Name which surface the claim concerns: basis, basis-hermes, basis-jcode, steward, or corpus pressure.
2. Cite a safe source: commit metadata, safe filename, test result, generated-artifact path with provenance label, or existing wiki source page.
3. Mark whether the claim is:
   • observed evidence;
   • synthesis;
   • plan;
   • caveat;
   • no-go criterion.
4. If .basis is involved, use counts/status only unless a separate review approved the body.
5. If recovered Codex or app-server logs are involved, cite only branch/session/worktree metadata, safe filenames, aggregate status fields, and generated-artifact paths; do not publish raw turn bodies.
6. Run wiki lint before commit.
7. Keep the public page narrower than the private tree.

Basis-specific safety risks

Risk	Why it matters	Mitigation
Dashboard local-file access	basis-hermes dashboard routes can read a local source path and write output directories.	Keep dashboard loopback-bound; document local-only posture.
Jcode dashboard run state	/api/state can expose run records, event summaries, and execution metadata.	Do not scrape/publish it without review.
Prompt and NDJSON artifacts	Real runs preserve prompts, model streams, stderr, and parsed packets for audit.	Count filenames only; summarize architecture.
Proposal/acceptance confusion	Proposed records can look authoritative.	Always say proposal until an explicit acceptance change exists.
Dirty/ahead repo state	Some Basis work lives in dirty or untracked Codex worktrees.	Architecture/status summary only until clean/reviewed.
Generated-image confusion	Recovered UI artifacts can look like literal accepted runtime screenshots.	Label them as recovered/generated UI artifacts unless separately captured from the live app.
Formatter/test/build gates	A green page can outlive the code state it cites.	Re-check gates before claiming current green status.

Relationship to other wiki safety patterns

This page follows the same public/private split used by spec-deep-dive-wiki-ingest-project and spec-deep-dive-index: public pages may contain synthesis, metadata, counts, repo references, and caveats; raw private artifacts stay private.

That distinction is not bureaucracy. It is the difference between analysis and accidental exfiltration.