Project documentation
Exocortex Guide
Installation, purpose, data boundaries, epistemic model, architecture, test standing, continuation, and licensing status.
1. Install and remove
- Download Exocortex v0.56.4-test on the Android device.
- Open the APK. If Android blocks it, permit installation from the browser or file manager used for this download, then open it again.
- Confirm the package name
com.toexperience.appbefore installing.
Remove Exocortex through Settings → Apps → Exocortex → Uninstall. Export anything that must survive before clearing app data or uninstalling; Android removes the app’s private database with it.
APK SHA-256: 149ff25490fef0829ca3063be3e2a1dbbaed865d9291e312c803134ddf62620c.
2. Purpose
Exocortex is a local personal archive. It imports user-selected records into a modular Android database, keeps their provenance, provides multiple domain views, and exports a versioned archive that carries data and reconstruction context together.
It is not a cloud account, social network, passive surveillance service, or autonomous biography generator.
3. Data and permissions
The Android manifest has no INTERNET permission. The installed application cannot make network requests. It stores its working database inside the app’s private Android storage.
Individual functions can request local access to selected images and video, legacy storage on older Android versions, contacts, call history, SMS, notifications, or boot completion. Android presents applicable runtime permissions to the user. A denied permission limits the corresponding importer or reminder rather than creating a network fallback.
The website receives only ordinary web requests for this page and the APK. It does not receive the archive.
The website defaults to Dark Gray. A first-party cookie shares only its Light, Dark Gray, or Pure Black choice across the `myforgeworks.net` family; local storage supplies immediate display and fallback behavior. This preference is not an account or visitor identifier and has no connection to the Android archive.
4. Epistemic model
| Standing | Meaning |
|---|---|
| Raw | Selected source material, retained without promotion into interpretation. |
| Extracted | Parsed observations that keep source and import-time provenance. |
| Inferred | Machine- or human-derived proposals that remain explicitly provisional. |
| Confirmed | Records or relations the owner has deliberately accepted. |
The rungs do not overwrite one another. Evidence can outlive a later interpretation, and polished wording does not upgrade a proposal’s standing.
5. Archive and AI boundary
Exocortex performs no semantic inference inside the Android app. An external AI can receive only a file-based, owner-selected question packet. Any return must cite the exact exported resources and arrives as proposals; the owner alone confirms them.
The current protocol uses strict versioned JSON, capability bounds, replay and deadline checks, atomic staging, and quarantine for invalid returns. Unknown fields fail closed. The AI receives no socket, account token, or direct database access.
Combined exports carry schema versions, a Charter, source references, access receipts, and continuation context. The archive is intended to remain legible to a future user, developer, or AI collaborator without depending on one chat session.
6. Limits and test standing
- This is an active test build, not a stable public release.
- Host verification passes with 133 Java sources, Android 34 compilation, fresh-schema and retained migration checks, DEX/source parity, and valid v1/v2/v3 signatures under the continuing test certificate.
- The package targets Android 34 and supports Android 6.0 or later.
- The v0.56.4 replacement logo interaction has not yet been physically verified on the Samsung test device.
- Populated upgrade migration, large real archives, complete restore, and broader device/OEM behavior still require hardware verification.
- The signing certificate is explicitly a development/test identity and must not become the production release identity.
7. Continuation
The canonical development checkpoint contains the complete recovered history, build reconstruction, source inventory, architecture documents, requirements ledger, checkpoint and test notes, signing warnings, verification output, and a continuation entry point.
Future work must begin from that checkpoint. Import is the primary entry path; Raw, Extracted, Inferred, and Confirmed remain distinct; the app keeps no internet permission; AI access remains an explicit export aperture; and new behavior must update the requirement, architecture, test, and checkpoint records together.
8. Licensing status
No public outbound licence has been adopted for the Exocortex test build or its source repository. Download access is not, by itself, a grant to redistribute, publish, sell, or create a public fork.
AGPLv3 for software and CC BY-SA 4.0 for documentation and non-code assets remain a proposal, not an operative licence. The project still requires an inbound-rights and dependency inventory, production-signing procedure, brand policy, and final licence files before a stable public release.