Recovery, custody, graph integration, productization, and controlled release architecture. A faithful standalone demo of the 13-page source codex dated 2026-08-01. This page reproduces its full section structure and makes its systems explorable. It is a demo built from the document, not the live estate registry itself.
Neuruh Hub | Registry explorer | Estate calculators | Try-it walkthrough | Share link
The thread began with a practical question: where was the document and collection containing the roughly 232 HTML sites and other local builds? The search exposed a larger reality. The local machine contains a significant estate of prototypes, engines, connectors, agent systems, harnesses, code packs, specifications, receipts, and deployment work that is not represented by a reliable registry or a controlled GitHub release pipeline.
The observed ~/neuruh-live hub had 227 artifact links at the time of the terminal check (source claim). Those entries are primarily symbolic links to original files spread across multiple directories. The hub is a viewing layer, not a canonical repository, not a deployment catalog, and not proof that each entry is unique or publishable.
Count check: 227 observed links against roughly 232 sites named in the opening question. That is a gap of 5, or 97.8 percent, using the calculator in section 13. Both numbers are source claims, not verified by this demo.
| Evidence item | What it proves (source claim) |
|---|---|
| Terminal count: 227 links | The local HTML hub is real and populated; the count is time-specific. |
| Symlink targets | Assets originate in Downloads, Desktop trees, workspace audit outputs, prompter, repository trees, and backups. |
| Permission-denied transcript | The artifacts path is a directory; executing the directory was the wrong operation. cd or open is correct. |
| Port 8091 transcript | The hub was already being served; starting a second server produced Address already in use. |
| Artifact inventory | The collection mixes original builds, third-party saved pages, copies, research, prototypes, dashboards, and receipts. |
| Screenshots | JARVIS, Field Pins, plat views, SPOT-CHECK, Plat-Lab, Continuity Cockpit, and Galaxy were not conceptual only; visual surfaces existed locally. |
| DATUM Codex | A deeper deterministic/probabilistic valuation architecture exists beyond the visible calculator surface. |
| FHUND operator manual | The broader Neuruh lane/layer model, boot services, governance, receipts, and human-fire doctrine already exist. |
| Control Plane v0.1 / v0.2 packages | A read-only registry and post-census consolidation layer were generated and fixture-tested in the thread. |
The estate is distributed across competing roots. Different roots may contain active repositories, copies, exports, generated builds, worktrees, backups, and stale forks. Modification time alone is not enough to determine the source of truth.
~/neuruh-repos~/neuruh-workspace/repos~/repos~/neuruh-vault~/Downloads~/Desktop and Desktop/Neuruh MasterMounted external volumesLocally mirrored cloud folders
A filename such as final, latest, or v6 does not establish authority. A folder may be newer because it was copied, exported, or touched, while the real Git history and deployment origin live elsewhere. Canonical selection must use repository history, content hashes, manifests, tests, deployment references, and operator decisions.
The estate has accumulated deployable or demonstrable work without a consistent path from local disk to governed release. The missing bridge is not raw coding capability. It is repeatable identity, packaging, decision, and publication infrastructure.
Eight axes. Use the filter to inspect one axis at a time. Every axis matters because it changes how an asset is inspected, packaged, released, or priced.
The thread did not invent an entirely new organism. It identified that the organism already had many organs, but lacked a reliable estate registry between disk and execution.
The missing layer establishes identity and custody before an asset enters the graph, factory, or release process. Without it, the graph knows concepts but cannot reliably answer which exact file, repository, version, hash, or deployment is authoritative.
| Layer | Question answered |
|---|---|
| Registry | What exists, where is it, and what is its current custody state? |
| Graph | How is it related to products, capabilities, repositories, decisions, runs, and deployments? |
| Ledger | What changed, when, by whom, and with what receipt? |
| Orchestrator | What should happen next? |
| Executor | What action was authorized and actually ran? |
| Release plane | What became externally available and how is it monitored? |
v0.1 indexed the current HTML symlink hub into SQLite, CSV, version-family reports, events, and a graph feed. v0.2 correctly moved the control plane after the broader census: it merges every complete census run under ~/neuruh-estate-census/ with the HTML hub, deduplicates by resolved canonical path, retains the newest record for each path, and serves a combined project/artifact dashboard.
project, artifact, product, capability, version_family, duplicate_group, repository, deployment, decision, run, receipt, source.
belongs_to, implements, capability_of, version_of, contained_in, duplicate_member, supersedes, depends_on, generated_by, deployed_as, blocked_by, validated_by, produced.
Build a canonical registry record the way the codex requires it: identity first, then classification, then a human decision. Fill the fields by hand or load a sample. The meter counts the 12 required fields below.
Three samples drawn from section 9. Each one is a source-described asset family, not a live registry row.
0 of 12 fields complete (0 percent).
Missing fields:
A record is not canonical because its name says final or v6. It is canonical only when path, hash, repository evidence, and an operator decision agree.
Share encodes the current record into the URL hash as base64 JSON. Anyone opening the link restores the same record in this demo. It shares only what you entered here.
Fifteen families recovered in the thread. Filter by treatment or search by name. Canonical treatment is the source recommendation, not a completed action.
The recovered estate can support multiple commercial forms. The business error would be forcing every artifact into a hosted SaaS product. Many tools can be valuable as static demonstrations, downloadable utilities, white-label components, or sales funnels.
| Commercial form | Best fit | Operating cost profile | Primary gate |
|---|---|---|---|
| Free lead magnet | Static HTML calculators, diagnostics, samples | Near-zero if browser-only and no paid calls | Ownership, claims, dependency audit |
| Paid static download | Offline calculators, reports, checklists | Near-zero marginal hosting cost | Packaging, license, support boundary |
| Hosted micro-tool | Form + API + stored result | Per-run API/storage cost | Unit economics, abuse control, monitoring |
| White-label license | Tenant-branded CRM or intelligence surfaces | Setup plus support; engine may remain centralized | Brand seam, data segregation, contract |
| API/engine | DATUM, valuation, scoring, evidence retrieval | Usage-based compute/data cost | Reproducibility, versioning, SLA |
| Internal engine surface | Core scoring, discovery, defense/private methods | Not sold directly | Firewall and private IP review |
| Sales demo / proof artifact | JARVIS, Galaxy, visual cortex, prototype screens | Low; used to convert prospects | Truthful capability labeling |
| Doctrine | Binding rule |
|---|---|
| census-first | Read actual disk/repository state before any mutation. |
| single-writer | Exactly one authorized writer per table or record domain. |
| AI-never-deletes | Automated jobs append or overwrite their own outputs; reorganization is move-not-delete and operator-gated. |
| human-fires-writes | Mint, merge, deploy, publish, and money-moving actions require an operator keystroke. |
| firewall | Engine IP, tenant data, credentials, defense work, and statutory/scoring methods do not leave the Mac without explicit review. |
| subdivide-the-brands | Neuruh engine, platform/terminal products, and tenant brands remain separable. |
| receipts-first | Core reports and proof depend on deterministic receipts, not optional LLM narrative. |
| keychain doctrine | Secrets migrate to macOS Keychain and are fetched at runtime; no plaintext secrets in published repositories. |
| dual-key naming | Canonical repository name plus pinned lane alias; every work item lands on the board with a stable identifier. |
| revenue outranks build | Recovered assets move toward validated commercial release instead of endless reinvention. |
| Phase | Objective | Exit condition |
|---|---|---|
| P0 Freeze writes | Allow census and registry operations only; no bulk moves or publication. | Census processes complete; outputs intact. |
| P1 Consolidate | Run v0.2 and merge complete census runs plus HTML hub. | Canonical project/artifact registries generated. |
| P2 Canonicalize | Resolve exact duplicates, version families, competing roots, and repository lineage. | Every priority asset has a declared canonical path and evidence. |
| P3 Protect | Run secret, ownership, license, private-IP, customer, and defense reviews. | No outbound candidate carries unresolved red flags. |
| P4 Package | Create clean repositories, READMEs, manifests, tests, screenshots, and sample data. | Release candidates pass local packaging gates. |
| P5 Stage | Create private/public GitHub staging, preview deployments, and acceptance receipts. | Operator can review real links and diffs. |
| P6 Ship | Human-approved publication, release tags, deployment, and monitoring. | External asset is live and registered back into Galaxy. |
| P7 Monetize | Connect assets to funnels, sales, licenses, and usage measurement. | Revenue/lead evidence is captured per asset. |
All ten metrics from section 13, with the share math the source defines. A share is: part divided by total, times 100. Enter census numbers to compute the first four. The other six are defined here and scored by hand in the registry, because the source gives definitions, not numeric inputs.
Share of eligible roots scanned and represented in registry.
Unique content hashes versus duplicate instances.
Version/duplicate families lacking an operator decision.
Candidates with README, license, source, tests, manifest, and screenshots.
227 observed links against roughly 232 sites named in the opening question.
| Decision | Status | Reason |
|---|---|---|
| Treat neuruh-live as a viewing layer, not source of truth. | LOCKED | Entries are symlinks to mixed origins. |
| Use read-only census before any move or publication. | LOCKED | Disk is truth; memory and names drift. |
| Do not bulk-create GitHub repositories from raw folders. | LOCKED | Would publish duplicates, secrets, vendor pages, generated output, and unclear lineage. |
| Run v0.2 only after census processes finish. | LOCKED | It merges completed runs and refuses to race the census. |
| Keep registry, graph, ledger, orchestrator, executor, and release responsibilities separate. | LOCKED | Prevents another opaque monolith. |
| Do not write directly into live Galaxy until its schema is read and mapped. | LOCKED | Graph mutation without schema proof risks corruption. |
| Keep JARVIS as the operator experience, not the authority layer. | RECOMMENDED | Registry and receipts hold truth; JARVIS retrieves and proposes. |
| Select canonical APG prototype before deriving white-label editions. | PENDING OPERATOR | Multiple versions exist and each may contain useful modules. |
| Keep QFA experimental/private until validated. | RECOMMENDED | Visual and conceptual value is not proof of scientific or production claims. |
| Risk | Failure mode | Mitigation |
|---|---|---|
| Duplicate publication | Multiple versions appear as separate products. | Hash grouping, version families, canonical decision receipt. |
| Secret leakage | API keys or local env files reach public GitHub. | Path/content scanning, Keychain migration, explicit secret gate. |
| IP leakage | Core scoring or defense logic is published with a demo. | Private-IP classification and component firewall. |
| Vendor-content publication | Saved webpages are misrepresented as Neuruh software. | Third-party reference classification and do-not-publish state. |
| Generated-build publication | Compiled HTML/dist is shipped without source. | Source/package manifest gate. |
| Graph corruption | Automated import deletes or overwrites historical nodes. | Upsert by immutable IDs; never infer deletion from absence. |
| False capability claims | A local frontend is described as a functioning backend. | Separate observed UI state from verified runtime/API state. |
| Cost blindness | A static tool calls paid APIs or maps. | Dependency and per-run unit-economic audit. |
| Operator overload | Hundreds of discoveries become another unranked backlog. | Priority scoring by revenue, uniqueness, maturity, and strategic reuse. |
| Endless rebuilding | New versions are created instead of shipping canonical assets. | Freeze version families and impose weekly release throughput. |
Five steps, in the order the codex requires. Use the buttons to move through them.
Run a read-only census before any move. In this demo, load Sample B (DATUM) in the explorer above and note that its path and hash are placeholders, not census output. A real census would supply the resolved path and SHA-256 hash.
Use the taxonomy tabs in section 4. DATUM is a valuation capability, an engine role, and an API/engine commercial form. Classification is what makes the estate searchable by function instead of by folder name.
Press Update completeness in the explorer. Sample B fills 10 of 12 fields. The missing fields are the operator decision and one classification gap, depending on what you edited. Nothing ships while required fields are missing.
Check section 8.4. Canonical-version selection, secret review, ownership and license review, public/private decision, GitHub publication, and production deployment all require a human. JARVIS proposes. AXON proposes. The operator fires.
Press Copy share link in the explorer. That link restores this exact record. In the real program the next step is P5 staging: a private or public GitHub staging area, a preview deployment, and an acceptance receipt, then registration back into Galaxy.
Step 1 of 5
Related: Neuruh Hub (master map of Neuruh sites). Sibling codex and system demos are listed on the hub. No other sibling URL is asserted here, because the source PDF does not name live sibling demo URLs.
Source: NEURUH LOCAL AI ESTATE - MASTER CANONICAL CODEX, MASTER-CODEX-001, 2026-08-01, 13 pages. Owner: Jeramie Hicks | Neuruh LLC. Status: Canonical working reference. Private operator working document.