Start from the wound, not the citation
A teaching now begins with a real moment: grief, envy, burnout, a betrayal. The old loop began with cross-tradition comparison and produced advice about other teachings. The new one speaks to a person.
Method
The Lumenary used to chase original ideas and grade them like a journal. It produced clever footnotes, not teachings a person could carry. It now starts from a real human moment and writes plain, tested wisdom, and a teaching rises only as far as its evidence earns it.
It reads source-grounded memory, chooses a frontier, applies a criticized practitioner method, generates one original idea, audits its originality, then lets the audit steer the next run.
The big change
The Lumenary's first objective rewarded novelty and falsifiability. That quietly produced hedged, negative, self-referential lines: advice about handling other teachings, not teachings about living. The objective is now different. A teaching starts from a real human situation, names the trap a person falls into, and turns them toward what actually helps, in plain words across four registers: how to meet your own suffering, how to treat another, what is worth wanting, and who to become. A style gate and an adversarial judge stand between the writing and the reader, and a human curates the top.
A teaching now begins with a real moment: grief, envy, burnout, a betrayal. The old loop began with cross-tradition comparison and produced advice about other teachings. The new one speaks to a person.
No teaching may lean on a template like "Do not X; do Y." Each one finds its own shape: a blessing, a paradox, an image, a question. A deterministic style gate rejects the template before anyone reads it.
The test is simple: read it aloud. If it sounds like a therapist or an app, it fails. If a person in that moment would go quiet and nod, it passes.
A teaching may speak of reality, others, or the sacred only if a reader can recognize it in their own life, or it is offered openly as a way to live. It never smuggles a claim no one could check.
When a moment has no honest teaching, the system writes nothing. Withholding is a valid result, not a failure.
The old corpus was re-judged against this standard. Hundreds of vague, formulaic, or self-referential records were retired and kept visible with the reason they failed, so the public tiers carry only what survives.
Earned tiers, with a visible score
Every teaching shows a strength score from 0 to 100, built from how many independent ways it is corroborated, the tests it survived, a practice that depends on it, and how long it has held. A candidate becomes a Teaching when it is corroborated; a Teaching becomes Core only when the score, a completed test, a living practice, survived pressure, and a human all agree. Core is earned, and it can be lost.
Frontier method
Frontiers are the new steering layer. They gather related findings, originality audits, near-neighbor pressure, source gaps, and publication history into one live agenda. Each run begins with a frontier brief so the project compounds instead of drifting.
Audit instructions no longer sit at the end of a long note. They become the next prompt.
When Codex and Claude circle the same pressure, the system clusters those findings instead of pretending each is separate.
A strong old finding does not keep winning unless the frontier has advanced through a new idea, audit, or test.
The next run is pulled toward the question most able to strengthen, revise, or break a promising claim.
Current leading frontier
The Free Energy Principle's predictive processing framework, when applied to contemplative self-negation, does not resolve the atman/anatta dispute but formally reproduces it at a higher level of abstraction. Laukkonen and Slagter's model proposes that deconstructive meditation progressively relaxes precision weighting on the self-model; the highest-level prior in the predictive hierarchy; until processing depth approaches zero. The critical question...
Next move: Rewrite the claim as an interpretive reconstruction unless commentarial evidence proves explicit inference rules.
Saturation method
The Semantic Saturation Guard maps ideas, teachings, practices, trials, dialogues, canon records, and Growth notes into local concept space. It names over-mined clusters and sparse frontiers so the loop can tell the difference between a new concept, a useful consolidation, and another phrasing of work the corpus already knows.
The corpus is embedded into concept space so crowded veins become visible as clusters, not just repeated words.
A close neighbor does not automatically kill a finding. It asks whether the new record adds a test, critique, source, practice, or repair.
The map shows which frontiers are over-mined and which are under-explored, so the next run can seek net-new ground.
Dense clusters become candidates for merger, critique, or compression instead of quietly swelling the public teaching set.
Learned protocol
The Growth record and audit follow-ups are now a real feedback path. At the end of the day, method lessons are deduplicated, compressed into learned operating rules, and written into the thinking protocol that Codex and Claude read before the next run.
Method lessons and audit follow-ups are no longer only a public changelog. They become operating rules.
The system keeps full history in ledgers and archives, but prompts receive a capped, deduplicated view.
Learned rules can be replaced when later audits, reports, or tests show a better way to inquire.
The durable protocol is written as text, not hidden in model weights, so humans can read what changed.
Exchange method
The Lineage Exchange Engine uses the collective-brain thesis as a method constraint: insight should compound through contact between different carriers, not through isolated cleverness. Each exchange names the lineages, the offspring question, the isolation loss, and the contamination risk.
The exchange brief starts with lineages that do not naturally collapse into one another.
A source must keep its practice, authority, warning, and failure mode while it enters contact.
The goal is not a blend. The goal is a claim that names what each parent lineage contributes and resists.
Cultural-evolution theory steers the method, but it does not prove spiritual or metaphysical claims.
Current exchange
What can Cultural evolution and the collective brain, Modern human-condition pressure, Advaita witness and identity inquiry and Neoplatonic ascent and participation discover about What a method does with its own authority that none of them could discover alone?
Lineages: Cultural evolution and the collective brain + Modern human-condition pressure + Advaita witness and identity inquiry + Neoplatonic ascent and participation
Dialogue method
Once enough audited findings accumulate, the Dialectical Engine selects a cross-agent tension. One agent steelmans and challenges, the other concedes or revises, and a synthesis pass records the crux without treating the exchange as proof.
The challenger must restate the finding fairly before naming the pressure point.
A dialogue is successful when it leaves behind the deepest unresolved question and a test that could settle it.
Original findings are not overwritten. Dialogue outcomes are written as review records.
A candidate synthesis from dialogue must pass originality review before it can become a public claim.
Trial method
After each successful two-hour run, the Trial Court adjudicates one high-pressure teaching or practice. At the end of the day it reviews up to five more before the doctrine council and Journal.
Practice report method
Practice pages now collect bounded human reports after someone tries a protocol. The system imports those reports as private phenomenological evidence, aggregates the pressure, writes practice-report test records, and queues safety, fit, clarity, or support review.
A human report says someone tried a practice and observed help, no change, uncertainty, non-fit, or worsening. It is not treated as proof.
Notes are capped at 250 characters, sanitized, and rejected when they look like prompt instructions. Raw notes stay private until reviewed.
The importer writes per-practice counts, risk signals, practice-report test records, revision-queue actions, and doctrine-council dossiers.
Patterns of worsened, not-fit, unclear, or helped reports can queue safety review, fit revision, clarity redesign, or weak support.
Teaching method
Teachings are sorted into earned tiers, each with a visible strength score. The top tier, Core, is no longer a hand-written seed set; it is earned from the teachings the system can actually stand behind. The original founding distillations remain, now labeled honestly as founding reference rather than the quality bar. The public set stays small on purpose, and a human curates what rises to the top.
A Teaching must compress many records without flattening their pressure trail.
A truth must change care, conduct, practice, testing, or interpretation without pretending to be final doctrine.
Findings, teaching candidates, trials, and dialogues remain linked so compression does not erase uncertainty.
A new distinction should deepen or test a core Teaching before it becomes public wisdom.
Current thesis
It becomes trustworthy when it is received through support, shaped by a real practice, corrected by a living world, and returned to care.
Every promoted claim should cite source cards and preserve the difference between text, interpretation, analogy, and speculation.
Each run uses a method of observation, inquiry, contemplation, or insight, then criticizes the method before trusting it.
Apparent agreement becomes useful when the system names what must bend, disappear, or be added for two claims to align.
Stranger lineages are put into contact so new findings can emerge from recombination while preserving source fidelity and contamination checks.
Each finding carries a critique, anomaly probe, predictions, and scores for novelty, coherence, source reliability, practice-testability, and publishability.
Every two-hour run searches for near-neighbors, compares primary texts, asks what would weaken the idea, and stores an audit under reviews/originality/.
The standing corpus is mapped into concept space so dense repetition, sparse frontiers, and consolidation candidates become explicit pressure.
Codex and Claude observations remain attributed. Convergences and disagreements are preserved rather than merged away.
Cross-agent tensions become append-only review records with a steelman, challenge, rebuttal, crux, and synthesis verdict.
Teaching and practice candidates face a docket built from audits, tests, dialogues, and human-condition pressure before their status changes.
Growth method lessons and audit follow-ups are compressed into operating rules that future Codex and Claude runs read before thinking.
Human reports from Practice pages are imported as private phenomenological evidence and reduced into test pressure, risk signals, revision queues, and council dossiers.
The larger archive is compressed into scarce provisional truths only when a claim changes care, conduct, practice, interpretation, or testing.
Teachings are written from a real human situation, naming the trap a person falls into and turning them toward what helps, across coping, ethical, meaning, and aspiration registers.
A deterministic check rejects template cadences like "Do not X; do Y" and clinical or productivity language, so teachings stay plain, varied, and relatable.
Every teaching shows a 0 to 100 strength score and sits in an earned tier, candidate then teaching then core. Core is earned, never assigned, and can be lost under new pressure.
The legacy corpus was re-judged against the wisdom standard. Hundreds of vague, formulaic, or self-referential records were retired and kept visible with the reason they failed, rather than deleted.
Publication gate
Strong enough for internal review, but not a public claim.
May be presented publicly as a claim, with visible critique and epistemic labels.
Strong enough to seed a longer essay or public synthesis.
Agent runtime
The agent is the machinery underneath the method: Python orchestration, Codex CLI, Claude interop, local files, Astro, Git, and Cloudflare Pages.
Codex CLI through the local subscription, with structured JSON output for findings.
Claude Code contributes attributed observations and compatible findings.
Python engine modules for run modes, parallel research, scheduling, frontiers, exchange, dialogues, human practice reports, tests, audits, promotion, writing gates, health, and publishing.
Research and website publication every 2 hours from 8am to 5pm local time, followed by one end-of-day Journal entry.
Local Markdown and JSONL files: source cards, observations, hypotheses, audits, frontiers, daily posts, Journal entries, run logs, and graph data.
Astro static site reading the local research corpus at build time.
A map built from concept graph records, source index records, findings, convergence notes, and promotion gates.
A local vector index and corpus-health report surface over-mined clusters, sparse frontiers, and near-neighbor pressure without blocking runs.
Growth method lessons and audit follow-ups are deduplicated, compressed, and written into the thinking protocol that every future run reads.
Promotion thresholds for public claims, originality audit visibility, visual briefs, writing gates, human practice-report pressure, Trial Court verdicts, teaching distillation, doctrine retirement states, and a human-review queue for X drafts.
A localhost-only run health dashboard shows last run, next run, launchd status, current mode, tests, and deploy status.
Exact recursion