New AI Language docs · static / Cloudflare Pages

agent.md — New AI Language project

Instructions for any human or coding agent working in new_ai_language/.


Mission

Build and document a representation stack for AI that is honest about architecture:

  1. Outer track (I/O): denser-than-prose text media (glyph / STATE-IR) so prompts cost less — still BPE text.
  2. Inner track (engine): architecture-native media for inference — Attention Output Cover (AOC / Manifold KV) and related frozen structures from the maths research — not “shorter English.”

Primary insight: models compute in continuous residual + attention outputs; English is a hostile codec into that geometry. Long-context cost is mostly KV (m·d), not paragraph style.


Goals (priority order)

#GoalSuccess looks like
1ClarityDocs explain arch + inference so a new agent never confuses prompt tips with engine representation
2Forced objectAOC (hybrid exact window + r* anchors of A(q)) is specified and linked to maths proofs/empirics
3I/O codecGlyph/STATE-IR runnable on traces (glyph_codec.py) for agent memory — labeled as Track A only
4Math fidelityCore theorems (Thm0 exact scores, covering of A, A0, hybrid, r_Σ gate) live under maths/ with source paths
5FindingsNew conclusions from thinking + experiments logged under findings/ — no silent drops
6No retrain defaultPrefer frozen drop-in / prompting / caching / tools; mark anything that needs training
7HonestyNever claim novelty or “magic free codec” without evidence; rediscovery is a valid result

Non-goals

  • Renaming EMA / RAG / summary as new primitives.
  • Claiming glyph is a non-text neural representation.
  • Shipping unvalidated “constant memory for all 7B long-ctx” claims (see brutal analysis).
  • Training soft prompts / new attention kernels unless explicitly marked needs train.

Folder map


new_ai_language/

  agent.md                 ← you are here (goals + how to work)

  README.md                 ← human entry

  docs/                     ← full explanations (arch, inference, tracks, formats)

  findings/                 ← synthesis + new conclusions

  maths/                    ← distilled theorems + excerpts from Research'

  refs/                     ← pointers to repo files / research paths


How to work (iron rules)

  1. Architecture first — residual, QKV, A(q), KV cost — before prompt slogans.
  2. Two tracks always labeled — I/O tax vs engine tax.
  3. Nothing disappears — dead ends → findings/ as failure or open_question.
  4. Cite sourcesResearch'/maths/... or memory/... paths.
  5. Falsify — every keep needs a kill test (tokens, A-error, or e2e task).
  6. Prefer implementable MVP — prototypes + kmeans anchors over full chirotope if scaling blocks.

Immediate build targets

  1. Keep docs accurate as code evolves.
  2. ~~Wire AOC MVP against harvested approx code~~ → done: new_ai_language/aoc/ (see findings/05_aoc_mvp_wired.md). Next: real raw_kv + HF hooks.
  3. Keep glyph_codec.py as Track A demo only.
  4. Append new empirics to findings/.

Related repo paths (do not duplicate blindly)

PathRole
Research'/maths/outputs/Full derivation corpus
Research'/maths/outputs/17_*.txtA(q) theorems
Research'/maths/outputs/HARVESTED_COHERENT_SPEC.mdPractical MVP
memory/FORCED_RESULT_WHY_TEXT_FAILS.mdArch synthesis
glyph_codec.pyTrack A encoder
codec_tesla_loop.pySignature transfer search
AGENTS.md (repo root)Lab discovery iron rules

Response style for agents

  • Mechanism-first, no hype.
  • Say when something is still text.
  • Say when something needs engine hooks.
  • Prefer tables and kill tests over poetry.