NeuroCognica
What You Get
For internal version 1.4.45 (build serial 62, unsigned) · Last updated 2026-08-03
This is the honest specification of what ChronoSophia does today — not a roadmap, not a wish list. Where something is unproven or absent, it says so.
The evidence named in section 2 was witnessed on earlier builds, as each row
states. The buyer-install witness was last attempted on internal build 1.4.38,
where it blocked at the Windows UAC consent screen. It has not been repeated
on 1.4.45. It is not presented here as completed, and the version this
document is pinned to is enforced by desktop/tests/test_customer_doc_claims.py
so the claim cannot quietly outlive the build it was made about.
Buy on what is in section 2. Treat sections 3 and 4 as not yet delivered.
1. In the box
- ChronoSophia — the desktop application (Windows 10/11, x64).
- Chronos Director — the local governance and pipeline daemon.
- The
chronosCLI — the same pipeline, scriptable. - The provenance ledger — BLAKE3 hash-chained, append-only, local.
- The full documentation set, including this honest capability accounting.
- A perpetual licence for one machine (EULA).
2. What is proven to work
These are capabilities the project has actually witnessed end-to-end, not merely wired up.
| Capability | Evidence |
|---|---|
Create tab → staged hero render — type a prompt, get a primary hero PNG with a saved .blend and a sealed manifest |
Earlier showroom render + UI witnessed 2026-06-21 on v1.2.0; the installed buyer witness remains pending on the current build |
| Named deterministic recipes — crystal spire, floating jawbone, canvas-on-easel, museum wall — chosen by the Display dropdown or by keyword in your prompt | Render-witnessed; deterministic and test-covered |
| Material intent enforcement — glass / metal / emissive / colour requests are honoured rather than silently ignored | Live-verified (red glass sphere) |
| Shape guard — nonsense geometry (a goblet as a torus) is corrected before it reaches Blender | Live-verified (goblet) |
Editable output — every render produces a real .blend with procedural geometry, plus PNG and an .s3v.json manifest |
Open them in Blender 4.5 without Chronos |
| Local-first creative operation — no cloud inference, no account, no phone-home for the creative path | Updates and optional dependency/model downloads use the configured vendor/feed URLs; prompts, renders, and ledger data are not sent as part of that path |
| Governance gate — the Sentinel authority + trajectory gate refuses unauthorised protected actions and seals the decision | Tested at the API level, enforce-by-default |
| Harmful-use refusal — every creation request is checked against a published four-category prohibited-use policy before anything is generated, fails closed if the local checker is unavailable, and seals the decision to your ledger. You see it clear the work on every run, not only when it refuses | Measured against the live classifier, both error directions, numbers and open findings published in SENTINEL_SECURITY_PROTOCOL.md |
| Your creative work is protected from the gate — fantasy violence, weapons, horror, satire, historical, medical and classical-nude subjects are defended by an explicit rule that overrides the classifier's own refusals | Same measurement; the false-refusal rate is reported alongside the miss rate rather than hidden |
3. The product is deliberately two pages
ChronoSophia ships Create and Gallery. That is the whole application.
Earlier builds exposed a conversational interview, a vistas browser, an animation and film-assembly room, an assembly workbench and a lineage graph. Those are removed from this release — not hidden, not "coming soon" behind a button that does nothing. The code remains in the repository, but nothing in the shipped app points at it, because none of it was finished to a standard worth charging for.
You are buying a focused tool: describe a thing, get a staged render and an
editable .blend, with provenance sealed underneath. Nothing on the two pages
is a placeholder.
4. Not in this release
Do not buy expecting any of these. They are named because pretending they are imminent would be the same lie as shipping them broken:
- Conversational interview with Sophia — removed from the rail; an unsolved research surface, not a product feature.
- Animation and multi-shot film assembly — pipeline code exists, output is not at release quality.
- Lineage graph browsing — removed. The sealed provenance record underneath is real and still written for every work; the graph view is not shipped.
- Assembly workbench / 3D-printer handoff — a separate product direction.
- Model fine-tuning — an operator-grade pipeline, excluded from the install.
Two known defects, stated plainly:
- The Windows uninstaller has been run for real once, and it is not yet proven clean. On 2026-08-02 it was executed with a real buyer's choices (remove the tools, keep the models). What it got right: 28 GB of models, 329 MB of artwork, and every pre-existing tool were left untouched — the data-preservation contract held. What it got wrong: five defects, the worst being that it printed "removal complete" while 5.4 GB was still on disk, because it could not remove ComfyUI while ComfyUI was running. All five are fixed in 1.4.45. A clean cycle on the fixed build has not been re-witnessed, so we still do not claim the uninstaller is proven.
- The installer is not code-signed. See section 6.
5. What you must supply
| Requirement | Detail |
|---|---|
| Windows 10/11 x64 | Build 18362 or later |
| 16 GB RAM | 32 GB recommended |
| NVIDIA GPU | Strongly recommended. CPU-only works but image generation is very slow. Fine-tuning needs 12 GB+ VRAM |
| ~30 GB free disk | For the third-party dependency toolchain |
| Third-party tools | Blender 4.5 LTS, ComfyUI, Ollama, Python 3.11, Rust, Git, LLVM, MSVC Build Tools — the installer fetches these from their own vendors with your consent, roughly 15–30 GB |
| AI image checkpoints | Not bundled in the installer binary. The setup task can, with your explicit checkbox consent, reuse verified matching files from an existing local ComfyUI model library or fetch the required files: Flux schnell on NVIDIA (~29 GB) or Z-Image-Turbo nvfp4 on CPU (~10 GB), both Apache-2.0. Recipes that need image models refuse to render rather than hand you a blank canvas. See MODEL_LICENSES.md |
| Patience with a first install | The dependency setup is long. This is a local AI toolchain, not a 40 MB app |
The one model that installs automatically is qwen2.5:7b-instruct (Apache-2.0),
which turns your prompt into a validated scene plan.
6. Two things to know before buying
The installer is not code-signed. Windows SmartScreen will warn you, and Defender has quarantined it as a heuristic false positive on at least one clean machine. Verify the SHA-256 of your download — see VERIFY_DOWNLOAD.md. This is disclosed rather than hidden; signing is pending certificate procurement.
CPU image generation can take close to an hour. The Create tab uses a 90-minute no-image safety watchdog; it does not promise GPU-like latency.
FLUX.1-dev is not licensed for commercial use of the model. The product
default is FLUX.1-schnell (Apache-2.0), which is fine for commercial work. If
you switch to dev via CHRONOS_FLUX_VARIANT=dev, that is your licence decision
to make with Black Forest Labs.
7. What makes this different
Not "AI generates 3D" — plenty of tools do a version of that. The distinctions:
- The output is editable. A real
.blendwith procedural geometry, not a mesh blob or an image. - Everything is local. Your prompts and work never leave your machine. There is no service to lose access to.
- Every artifact carries provenance. Prompt, seed, plan, and policy decisions are sealed in a tamper-evident hash-chained ledger you can verify.
- Actions are gated before they execute. Out-of-plan commands are refused and the refusal is recorded, rather than trusted and hoped for.
If none of those matter to your work, this probably is not the tool for you, and we would rather you knew that before paying.
8. Why this document exists
Most software tells you what it might do. This tells you what it does.
Section 2 is the promise. If anything there does not work on hardware that meets section 5, that is a refund — see the Refund Policy, no argument required.
Sections 3 and 4 are the things a demo video would let us quietly skip. They are here because you deserve to decide with them in front of you.