🔭 Meta¶
This folder has two lanes so we don't mix conceptual reflection with repository governance:
- Conceptual Meta (epistemology, philosophical framing)
- Repository Meta (governance, contribution and structure rules)
Meta Inventory (current files)¶
| File | Lane | Purpose |
|---|---|---|
conceptual-meta/agent-prompt-seed.md |
Conceptual Meta | Exploratory prompt artifact for autonomous identity seeding. |
repository-meta/repository-information-architecture.md |
Repository Meta | Canonical placement rules and lane-splitting logic for the whole repo. |
repository-meta/repository-as-thought-system.md |
Repository Meta | Meta-orientation: how the repo's own structure can be read without becoming self-referential noise. |
repository-meta/speculative-writing-guidelines.md |
Repository Meta | Speculative writing conventions (placement, labeling, continuity, style baseline). |
repository-meta/cultural-optimization-red-team-manual.md |
Repository Meta | Guardrails against Goodhart pressure in cultural optimization systems. |
repository-meta/core-claims.md |
Repository Meta | Minimal testable claim set with artifact links and failure conditions. |
If a future file does not clearly fit one lane, add a one-line "Lane:" declaration at the top of that file.
Conceptual Meta¶
Agent Prompt Seed¶
An experiment in autonomous identity seeding. A foundational prompt designed to initialize an agent with a set of thermodynamic and systemic axioms, forcing it to navigate the tension between entropy, growth, and alignment.
Repository Meta¶
Repository Information Architecture¶
Defines where new artifacts should live and how the repository keeps a coherent lane split.
Repository as Thought System¶
Defines the useful meta-level: the repo can be read as operator, iteration, form, boundary, and return path, but only to improve navigation and prevent drift.
Speculative Writing Guidelines¶
Lightweight conventions for placing and labeling speculative fiction/theory so new additions stay connected to existing concepts and formats.
Cultural Optimization Red Team Manual¶
A practical anti-pattern and review ritual guide for authenticity/care optimization systems.
Core Claims¶
The minimal testable claim set for the repository — Substrate Veto, Impedance Matching, Identity Persistence, and Vital Floors — each with artifact links and explicit failure conditions.
These notes are intentionally mixed in maturity level, but separated by function so conceptual essays and repository-meta documents don't blur together.