# AkashicNEXUS · Reddit Archive Import and Component Improvement Plan

**Edition:** v0.1.0 · Proposed implementation plan · 19 November 2026  
**Owner:** AkashicNET × u/NeuronsToNirvana  
**Destination:** The existing AkashicNEXUS architecture and restricted review workspace, with public-safe summaries on AkashicNET.org. No duplicate public hub.

## Purpose

Bring the complete retained account export into a searchable, traceable NEXUS workflow. Give every post and comment a source record. Review suitable posts as numbered inquiries and use observed weaknesses to propose, test and document improvements to NEXUS and its components.

Importing is different from reviewing, publishing or validating a claim. The complete retained export is the import scope; public publication remains a separate decision for each record and derivative.

## Verified Starting Point

| Measure | Saved export |
|---|---:|
| Posts | 8,767 |
| Comments | 12,347 |
| Total records | 21,114 |
| Subreddits represented | 132 |
| Communities containing posts / comments | 89 / 112, overlapping |
| Estimated words across the account | 2,319,816 |
| Estimated words within r/NeuronsToNirvana | 1,447,422, included above |
| N2N posts / comments | 6,645 / 3,046 |
| Retained date range | 18 June 2018–2 November 2026 |

The account’s earliest retained post is “Boom 2018 Dance Temple Inspiring Closing Speech”, 11 August 2018. N2N records begin on 30 March 2022 with a deleted entry, a test and then the *Neurons to Nirvana* trailer. These are export observations, not proof of complete account history.

Word-count method v1.1.0 counts titles, post bodies and comments after removing URLs, HTML tags, embed syntax and deleted/removed placeholders. It includes quotations, reused material, crossposts and any AI-assisted wording in the records. Linked article text, image text and transcripts are excluded. A correction removed 671 unavailable-title placeholders, reducing the earlier conversational total by 2,013 tokens. Approximate reading time for the retained account text is 155–193 hours at an assumed 200–250 words per minute; study and verification would take longer.

**Completed:** original export located; record counts reconciled against the existing monthly history; aggregate word count and growth chart produced. Existing public title imports and topic inventories can be reused within their recorded scopes.  
**Not completed by this plan:** production full-text ingestion, 21,114 individual NEXUS reviews, automatic semantic review, a durable operational ledger or independent validation.

## Boundaries and Record Model

Keep the original export and operational source records restricted. Exclude IP addresses and unrelated account tables from the working corpus. Store raw source and editorial derivatives separately. Preserve existing Restricted, withheld and HOLD states. Deleted or unavailable content stays unavailable; do not reconstruct it.

Each source record needs:

- Stable Reddit fullname: record type plus original ID, such as `t3_<post_id>` or `t1_<comment_id>`.
- Original date in UTC, displayed local date, subreddit, title where present, permitted text and original permalink.
- Parent/thread references, source snapshot checksum, field availability and deletion status.
- Import/review/publication states, audience, source-access status and links to derived runs.
- Content hash and version, so edited exports can be compared without silently replacing prior evidence.

An import operation must be replayable without duplicates. Missing parents can be represented by explicit unavailable-parent records. Deduplicate source IDs while preserving separate posts that share a title or URL. Connect crossposts as related records; do not count them as independent corroborating evidence.

## Inquiry Names and Numbering

Every source can receive a NEXUS run record. Only records selected for substantive inquiry receive a numbered AkashicINQUIRY. A link-only post may be routed for source retrieval; a test or deleted entry can receive a recorded disposition without a full inquiry.

| Community | Proposed inquiry namespace |
|---|---|
| r/NeuronsToNirvana | `AkashicINQUIRYN2N0001` |
| r/microdosing | `AkashicINQUIRYMICRO0001` |
| r/boomfestival | `AkashicINQUIRYBOOM0001` |
| Other communities | Code registered once in a shared namespace registry |

These are naming proposals, not allocated or published inquiry IDs. Keep them distinct from the existing AkashicINQUIRY publication series. Allocate serials transactionally, preserve them after revisions and never renumber earlier inquiries when older material is imported. Expand beyond four digits when necessary. Source IDs remain authoritative; inquiry numbers are editorial identifiers. Comments normally remain attached evidence or context, with standalone inquiries only where a distinct question warrants one.

## Delivery Phases

| Phase | Concrete output | Acceptance gate |
|---|---|---|
| 1 · Inventory and schema | Read-only inventory, import schema, community registry, source hashes and visibility mapping | Reconcile all 8,767 posts and 12,347 comments; distinguish missing fields and excluded private fields |
| 2 · Restricted intake | Idempotent importer into the existing owner-private datastore; original/derived separation; parent links; search index | Replaying a batch adds no duplicates; unauthorised access fails; interrupted imports resume; original records remain recoverable |
| 3 · Triage and routing | Chronological queue per subreddit, duplicate relationships, claim kinds and next-action states | Every imported record is queued, reviewed or given an explicit disposition; provisional topic labels remain provisional |
| 4 · Representative pilot | 30 posts and 20 comments across at least four communities, with old/new, link-only, long-form, quoted, missing and test records | Record source fidelity, reviewer effort, missed issues, false alarms and privacy outcomes; use synthetic restricted examples for public demonstrations |
| 5 · Numbered inquiry workflow | Faithful source view, attributed claims, source appraisals, optional relevant lenses, recommendations and rechecks | Every material finding has an evidence locator and reason; applied changes are distinguishable from proposals; independent review is separately recorded |
| 6 · Component improvement | Tested change candidates for NEXUS and affected tools; versioned releases and STATE decisions | Evaluate against frozen or held-out examples and the prior version; retain regressions, failures and reviewer disagreements |
| 7 · Scale and public summaries | Small resumable batches by community/date; authorised public summaries and source links | Counts reconcile, access boundaries pass, open actions remain visible and actual publication receipts are recorded |

The 50-record pilot is a proposed starting batch, not an executed test or a statistically representative sample. Choose the final sample and evaluation protocol before running it.

## What NEXUS Does for Each Selected Record

| Component | Contribution |
|---|---|
| MESSAGE | Preserve original wording and separate attributed statements from interpretation |
| TRACE | Retain origins, source locators, retrieval dates and unresolved provenance |
| INQUIRY | Form a bounded question, examine evidence and record what could change the answer |
| NEURO | Offer evidence-aware reflection where relevant; infer no individual biology from posting activity |
| SPIRIT | Offer an optional spiritual/esoteric reading with the named tradition, cultural context, alternative interpretations and freely chosen care; retain development status |
| PRISM / OMNI / Pyramid | Reframe relevant questions, compare perspectives and inspect foundations; do not require every lens for every post |
| ASSESS | Compare proportionate next actions and reopening conditions |
| ENHANCE | Propose or apply justified edits to the inquiry; separately propose changes to the method or tools |
| ABSTRACT / ONE | Produce a faithful summary and coherent handoff without losing uncertainty |
| TEST / AUDIT | Record actual methods, expected and observed results, evidence support, limitations and review roles |
| STATE | Reassess readiness only from relevant evidence; retain null or provisional scores where justified |
| LEDGER / FOOTPRINT | Link dated decisions, before/after versions, checks, releases and measured resource use; unknown costs remain unknown |
| FLOW / NEXUS | Route the work, manage handoffs, stop when the scoped task is satisfied and reopen affected stages when evidence changes |

AUDIT’s claim–source check uses supported, partly supported, contradicted and unresolved outcomes. Evidence availability is a separate field. An excerpt’s presence does not establish that it supports a claim.

## How the Archive Can Help Advance NEXUS

1. A review exposes a specific weakness: missing provenance, ambiguous claim support, poor routing, a false alarm, a confusing interface or an unnecessary repeated step.
2. AUDIT records the finding, affected component and scope, evidence, consequence and recheck.
3. ENHANCE creates a change candidate with a before/after comparison and a reason. Keep inquiry edits separate from tool changes.
4. TEST compares the candidate with the prior version using frozen or held-out cases, recorded settings and declared evaluation criteria. A separate reviewer’s assessment is recorded independently from the implementing author’s review.
5. A scoped release decision records what passed, what remains unresolved and whether the change is ready for use.
6. STATE retains, raises, lowers or leaves readiness unassessed according to the evidence. A successful import or a high self-authored test score does not automatically raise maturity.
7. LEDGER preserves the earlier edition, finding, implementation state, test results and confirmed release receipt. Regressions reopen the affected component.

This is an evidence-led improvement loop. The plan does not establish autonomous self-improvement or general reliability. Failure cases are valuable inputs and remain visible. The unavailable-title word-count correction is one concrete example of a data-quality finding informing the counting method.

## Progress and Evaluation Dashboard

Track these separately by community, record type and date cohort:

- Records discovered, imported, duplicated, missing and excluded.
- Records queued, triaged, reviewed, deferred and HOLD.
- Inquiries drafted, checked, approved and actually published.
- Source coverage, broken references and unresolved claim–source judgements.
- Recommendations proposed, implemented, rejected and awaiting recheck.
- Issues caught, missed issues and false alarms under the declared evaluation protocol.
- Reviewer agreement/disagreement, observed review time and whether the reviewer helped author the method.
- Component editions, readiness changes with reasons and outstanding actions.
- Measured model usage, external retrieval, storage and direct costs where telemetry exists. Do not invent carbon, energy or labour measurements.

Do not combine import completion, review completion and public availability into one percentage.

## Scheduling and Resource Decisions

Measure time, token use and rework on the representative pilot before forecasting the full import and review programme. Keep intake, AI review and human editorial effort separate. Batch size should follow measured capacity and error recovery, not a promise to review every record immediately.

The public site has already approached its deployment-package size limit. Keep the full-text store and retrieval index out of its static deployment bundle. Reuse the existing restricted app’s datastore and access model after confirming their current schema and permissions; publish lightweight approved summaries and aggregate charts on the existing public site.

## Release Checklist

- Source counts reconcile and duplicates are controlled.
- Original dates, IDs, source links and field-availability states survive import.
- Private fields are excluded from the working/public projections.
- Unauthenticated and unauthorised users cannot retrieve restricted records.
- Replay, interruption recovery, revision history and restoration are demonstrated.
- Public search exposes only authorised public content; Restricted/HOLD work remains visible only within its authorised scope.
- Inquiries preserve evidence status, attribution and original/derived distinctions.
- Proposed improvements, implemented changes and observed outcomes are distinct.
- Earlier pilot records and unsuccessful tests remain available in the appropriate audience.
- Build, links and actual publication are verified before reporting a release.

## Immediate Next Deliverable

Implement the restricted importer and a 50-record pilot queue in the existing NEXUS review workspace. Start with the earliest retained account material and the N2N founding-day records, then include other communities and later examples. Record a disposition for the deleted/test entries rather than fabricating their content. Proceed to scale only after the intake and review gates pass.

**Current decision:** chart and plan prepared; full-text production import and per-record reviews are planned. No bulk public archive release or component readiness increase is claimed.

## Personal Origin and Public Presentation

Creative title: **AkashicNEXUS · Step into the Future**. Working description: **Hybrid Spiritual Intelligence · Human-led · AI-assisted · Evidence-aware**. This names the approach, not an evaluated technical capability.

The founder reports an NDE-like revelation in a hospital bed at about 3am on Easter Monday, 1 April 2024: an Akashic library. That experience motivates the practical, source-linked digital library; it does not establish a metaphysical library as fact. The retained Reddit Tesla/higher-intelligence post is dated 29 March 2024 (three days earlier): https://www.reddit.com/r/NeuronsToNirvana/comments/1bqbz5k/nikola_tesla_believed_his_dreamsvisions_came_from/ . Its source X Snowflake ID 1771877157456728450 decodes to 24 March 2024, 12:30:08.880 UTC (eight calendar days earlier). This is an ID-derived date; live source content was inaccessible. Encoding: https://github.com/twitter-archive/snowflake/blob/snowflake-2010/src/main/scala/com/twitter/service/snowflake/IdWorker.scala .

The chart combines measured cumulative word estimates with a separate topic vocabulary view: 521 provisional labels in 12 overlapping editorial groups, from the public-title snapshot of 3 November 2026. Four inner families are new display groupings, not validated latent categories. Ring shares describe label counts, not distributions of posts or words.

Soundtrack: Sonic Species & Yushi — Digital Reality (official video), https://www.youtube.com/watch?v=nvh4_-vrl8E , track 5 of Psy-Nation Radio 104, https://www.youtube.com/watch?v=UH_Ju6ehtbc . Click-to-load embed, no autoplay. The creative tagline was supplied by the curator; a lyric transcript has not been verified.

The neon mycelium city and festival artwork is AI-generated fantasy inspired by Tribal Gathering, Panama. Stage adjacency is conceptual, not a verified map. The corner dedication thanks 6Monkeys; it does not attribute production or imply endorsement. Public professional credits: https://www.instagram.com/6monkeys.collective/ and https://www.youtube.com/@KrischandeBeer . Westworld S3E5 “Genre” is a proposed cinematic transition reference; the current still does not implement that animation.
