Systems Architect · Evidence Engineer · AI Governance & Assurance
Founder and lead architect of CASTÚO-SYSTEM™
I design offline-capable systems that preserve data provenance, integrity checks and explicit boundaries for AI-assisted decisions.
No claim without provenance. No external claim without reproducible evidence.
Try the browser demo (synthetic v0.1.1) · e3bundle source · Contribute · Community
| Focus | Tools used in the linked artifact | Start here |
|---|---|---|
| Portable evidence verification | Python · SHA-256 · Ed25519 · JSON | e3bundle alpha and its limits |
| Understandable decision boundaries | HTML · SVG · synthetic JSON cases | Local governed explorer |
| Reviewable engineering documentation | Markdown · YAML · provenance and acceptance criteria | Public evidence dossiers |
Current focus: make verification easier to reproduce, explain failure and abstention clearly, and improve contribution paths in English and Spanish. The linked artifacts show the scope of this work; they do not establish independent validation or production readiness.
e3bundle is a small MIT-licensed Python CLI for creating, signing and verifying portable evidence bundles offline.
- Records file digests in a SHA-256 manifest and detects changed, missing or undeclared files.
- Verifies Ed25519 signatures against explicitly configured trusted public keys.
- Produces bounded, machine-readable results for automation and review.
Scope warning: These examples are synthetic and locally verifiable. They demonstrate bundle integrity and signature-policy checks only. They do not validate field data, operational performance or production readiness.
The repository contains two synthetic signed example bundles: valid and tampered. The tampered example changes one value in data/readings.csv.
After following the bounded source-evaluation setup in the current e3bundle README, run from the repository root:
e3bundle verify examples/bundles/valid --min-signatures 2 --trusted-keys examples/bundles/trusted-keys.json --format text
# Expected: VERIFIED · exit 0
e3bundle verify examples/bundles/tampered --min-signatures 2 --trusted-keys examples/bundles/trusted-keys.json --format text
# Expected: FAILED · hash mismatch in data/readings.csv · exit 1The CLI release v0.1.3 is an alpha. This source-level path is for bounded evaluation, not a general production-install recommendation. The browser demo runs synthetic v0.1.1 examples locally; it is useful for trying the interaction, but does not validate the v0.1.3 CLI.
For a reproducible hands-on example, follow the English dataset-tampering tutorial or the Spanish guide. It creates a synthetic signed dataset and shows how the verifier rejects edits, added files and missing files; it does not count as external field validation.
A VERIFIED result means that:
- The declared files match the SHA-256 manifest.
- No required file has been detected as changed or missing.
- The configured signature policy has been satisfied.
- The supplied trusted-key configuration accepted the required signatures.
It does not prove that:
- The underlying content is true.
- The evidence was collected correctly in the real world.
- The signer's real-world identity has been independently confirmed.
- The operation was performed in the field.
- Independent third-party assurance, production readiness or regulatory compliance has been established.
Integrity verification is one layer of assurance, not complete validation of the underlying event or claim.
CASTÚO-SYSTEM explores optional database/API integrations, including Supabase, but no deployed production integration is claimed. The public profile intentionally does not expose the live project endpoint, database connection strings, secrets, private infrastructure or customer data. A project API URL is not a database password; frontend access still requires correct RLS, limited privileges and security review.
Read the publication and Supabase disclosure policy before proposing public-facing integrations.
The public tool is an alpha, not a production-approved release.
- Independent E3-001 reproduction:
PENDING. - Publication and deployment gates remain open.
CONSOLIDATION-1.0 = BLOCKED.
Traky12 is the public read-model, not the technical authority. Castuo-system is the private canonical authority for technical state and promotion. castuo-evolution is a non-canonical workspace.
For dated evidence, unresolved gates and workflow history, see the public status detail. Current capability must not be confused with maturity: DOCUMENTED ≠ IMPLEMENTED ≠ TESTED ≠ VALIDATED ≠ OPERATIONAL.
GitHub · @Traky12 · LinkedIn · CASTÚO-SYSTEM
Explore the data: local interactive explorer: six synthetic cases, step-by-step checks, abstention reasons and JSON export. Download the HTML and open it in a browser; GitHub displays its source rather than executing it. The interface is in Spanish.
Spanish animation preview · 10 s · Higher-definition video
This is a conceptual simulation: sources, thresholds and queue timing are illustrative, not measurements or live integrations. It does not represent field validation, autonomous action or production readiness. Read the scope and evidence questions for detail.
| Project | Purpose | Current boundary |
|---|---|---|
| e3bundle | Offline SHA-256 manifest and Ed25519 signature verification | Alpha; integrity checks are not a truth claim, certification or production approval |
| castuo-agro-edge | Offline-first edge/IoT runtime experiments | Field validation is not claimed |
| castuo-evidence | Bounded public evidence package and replay material | Independent replay and human review remain pending |
| Cast-o | Software-assurance and testing tooling | Benchmarking is not evidenced; licensing remains under IP review |
For the e3bundle onboarding sequence, adoption gates and the Starstruck visibility milestones, see the public adoption roadmap. The roadmap is a work plan, not evidence that its gates have passed.
The following are not claimed:
- Independent reproduction of E3-001.
- Field validation.
- Production validation.
- Third-party conformity assessment.
- Regulatory conformity.
- Paid-customer traction.
- Recurring revenue.
- Production AI autonomy.
- Production readiness of the current alpha artefacts.
Capability is not maturity: DOCUMENTED ≠ IMPLEMENTED ≠ TESTED ≠ VALIDATED ≠ OPERATIONAL.
Start with one bounded, reproducible contribution:
| Your interest | Useful first step |
|---|---|
| Documentation and accessibility | Describe one confusing step, its location and a proposed correction in a profile issue. |
| Python and verification | Read the current evaluation setup, then choose an existing scoped issue. |
| Independent review | Read the review requirements and current gates before proposing a review. |
Use synthetic or public data. A first contribution needs no private-repository access or credentials. Check whether an issue is paused before starting; independent-review status changes only after the formal evidence is accepted.
- Profile contribution guide · e3bundle contribution guide
- Report vulnerabilities privately
- Full repository map · Public claim boundary · Evidence index
For technical collaboration, independent review or pilot discussions:
- LinkedIn: CASTÚO-SYSTEM™
- GitHub: @Traky12
Traky12 is the public read-model. Canonical technical state and promotion decisions remain in the private Castuo-system repository.




