Engineering portfolio and public record

Public provenance record

This site is a public evidentiary record for the coded engineering portfolio. Its purpose is to preserve chronology, authorship, current control position, broad functional boundaries, maturity and selected cryptographic commitments without publishing enabling implementation detail.

The coded register remains the primary public presentation. Conventional project names, private filenames, employer/client/site records and detailed implementation methods are not used as substitutes for the controlled code structure.

Current sanitised disclosure

3 October 2026. BDXT-PUB-001 Revision 1.6 is the current coded public technical/provenance disclosure. Its title-page architecture graph now shows the principal project codes as separate linked nodes rather than grouped blocks.

The E-series remains disclosed as a small shared kernel beneath the A/B/C/D domain systems, not as a parallel catalogue of end-user products.

Open current public record →

Controlled source commitment

The 3 October architecture append is backed by a privately retained controlled source. The source file itself is not published. Its SHA-256 commitment is:

Open Core Release 001

Current Open Core release. DrillFlowCore, BBIPEvidenceCore, EFSTagCore and ExplorationEvidenceCore are published as a limited interoperability layer under MPL-2.0. These are public source components mapped back to the coded portfolio; they are not additional portfolio identities.

Open source record →

Public doctrine

1. Evidence before claim.
2. Observation, inference and authority remain distinguishable.
3. Conflicts and limitations are surfaced rather than silently hidden.
4. Promoted engineering states are versioned and evidence-backed.
5. Shared cross-product primitives remain small; domain ownership remains explicit.
6. Restricted, third-party and externally governed material remains outside proprietary claims.