# AkashicNEXUS Reference Package · v0.1.1

Bronze Edition · Provisional Overall Maturity 6/10
Defined 19 November 2026. Package version, component versions and maturity are separate.

## Open The Package

Unzip and open `editions.html` in a browser. Open `index.html` for the existing workflow guide. Local CSS, JavaScript, sigils, artwork and diagrams are included. No installation is required. External source links need a network connection; private workspaces may require sign-in.

For optional localhost serving, from the extracted directory run `python3 -m http.server 8000 --bind 127.0.0.1` and open `http://127.0.0.1:8000/editions.html`. Python 3 is required only for this optional command. Stop with Ctrl+C.

## Run A Guided Review

1. Choose one proposed case in `package/test-cases.json`, or define your own scope and stopping conditions.
2. Preserve the original wording and source locators. Decide the audience and the relevant lenses.
3. Use the packaged prompts and guidance with a model or human reviewer of your choice. `package/components.json` preserves all 13 component contracts. `package/prompts/` preserves the five complete published reusable prompts without rewriting them.
4. Copy `package/state-record-template.json` into your own working directory. Fill only fields established by actual evidence. Preserve the previous record when rerunning.
5. Record before-and-after changes, check methods, observed results, unresolved gaps and actual delivery separately.
6. After every NEXUS or STATE run, complete the post-run review handoff in `package/post-run-review-protocol.json`. Invite owner review, record independence and answer exposure honestly and keep ratings evidence-based.
7. Apply the same input and access conditions to baseline and NEXUS comparisons. Keep proposed tests marked Not Yet Run until executed.

This package does not call a model, store secrets, enforce access controls or publish content. Those functions require a future runtime. Templates contain null values intentionally. Source URLs are preserved context, not a claim that destination content was freshly audited.

## Contents

- `editions.html`: editions, ratings, AkashicSTATE, taxonomy and package blueprint
- `index.html`: full existing workflow, directory and reusable prompts
- `akashicnexus-orchestra.svg`: exact architecture visual
- `akashicnexus-bronze-workflow-v0.2.0.svg` and `.png`: detailed workflow
- `images/akashicnexus-bronze-sigil.png`: original AI-generated Bronze artwork
- `package/components.json`: component guidance, versions, classification, sources and ratings
- `package/editions.json` and `assessment-rubric.json`: grading definitions
- `package/akashicstate.json`: the module's provisional self-assessment
- `package/state-record-template.json`: blank reusable state record
- `package/test-cases.json`: three unexecuted acceptance cases
- `package/DEPLOYMENT-BLUEPRINT.md`: proposed executable architecture
- `package/SHA256SUMS.txt`: packaged file integrity hashes

## Rights & Attribution

No open-source or blanket commercial reuse licence is granted by this reference export. AkashicNET names, original materials and third-party source content retain their existing rights. Seek the relevant permissions before redistributing or commercially reusing protected content. Remote source works and private user data are not bundled.

## Public Release Boundary · 19 November 2026

This export contains public reference guidance and generic examples only. Source Atlas implementation, private metadata records, corpus data, credentials, telemetry and client records are excluded. Basic source locators and credits remain public attribution. See `release-boundaries.html` and `package/release-boundaries.json` for the qualitative maintenance review. Managed extensions are not shipped or priced.

## Post-Run Review Protocol · v0.1.0 · 19 November 2026

After every AkashicNEXUS or AkashicSTATE run, including reruns, finish with a Post-Run Human Review handoff. Invite Jatinder Sahota to review as Creator / Owner-Reviewer. This is a separate human review; creator involvement means it is not independent external validation. Offer an answer-free packet where suitable and record whether answers were actually hidden, seen or unknown. Record the run ID and edition, scope, reviewer role, method, date, judgements, disagreements and reasons, corrections and rechecks. Keep Owner Review and Independent External Validation as separate statuses; use Pending until actual evidence supports another status. Preserve dated before-and-after records in AkashicLEDGER or the current versioned record. Owner review may support a justified AkashicSTATE reassessment but never raises ratings automatically. Respect the authorised audience, private source metadata and existing HOLD boundaries. This adds a required handoff, not a new publication permission gate.
