Skip to main content

Blob and Secure Document Reference Status

To build an attachment feature, start with Upload, Save, and Read Attachments with Blob. It includes a runnable Java example with a PDF contract and PNG cover, plus replacement and removal. This page keeps the implementation and release evidence separate from that developer workflow.

For editable business data, use Open, Edit, and Submit a Protected Order Document. It runs the separate secure module without Blob and includes the application-owned SQL document service.

Runnable Java secure-order guide — 2026-11-01​

The downloadable order example ran at Java af59bf4ee6f003f509ce8cc42a5d96bb5dcdb8c3 with the companion upstream SQLite service copied byte for byte. Nine receipts cover open, projection validation, actor mismatch, rollback, successful quantity update, exact-command replay, stale-command rejection, explicit removal and current permission revocation. Native output and source/input hashes are public. This is a terminal JDBC service example; generated Q/E, HTTP, Blob selection, expiry/rotation and deployed migration are outside this run.

Runnable Java attachment guide — 2026-11-01​

The downloadable example was compiled and executed against Java source af59bf4ee6f003f509ce8cc42a5d96bb5dcdb8c3 with PostgreSQL, File storage and its HTTP gateway. It checked two independently typed fields, actual byte retrieval, stable SQL Keys, replacement, clearing and committed presentation failure. It uses explicit runtime metadata rather than a generated model. The execution receipt records source, input hashes, native output and cleanup. This is source-preview example execution, not public package or production-deployment qualification.

Seven-runtime implementation snapshot — 2026-10-31​

This is a maintainer summary captured on 2026-10-31 from the committed TeaQL conformance snapshot d1fea7720fbca946e57e7806b9172e6bc65e28ab. The conformance repository is private, so its raw logs and detailed test receipts are not publicly downloadable. The public runtime source branches below show the implementations under review. This page is an evidence snapshot, not a published-package or support-lifetime promise.

RuntimeSource under reviewReference modules
Javateaql-java#274Separate Blob and secure-document modules; local source and generated-consumer evidence
Rustteaql-rs#315Separate Blob and secure-document crates; local source, native package, and generated-consumer evidence
TypeScriptteaql-ts#62Separate optional module entry points; local source and artifact consumers
Goteaql-golang#60Separate optional packages; local source and artifact consumers
Pythonteaql-python#67Separate optional distributions; local source and artifact consumers
.NETteaql-dotnet#67Separate optional projects; local source and artifact consumers
Swiftteaql-swift#54Separate optional products; local source and artifact consumers

The five-language extension used generator revision 584c704bb349917a08adeffed64974749a059bd8 and runtime revisions TypeScript 15b10a271871, Go 6d8cf520b85a, Python 5b60c27310cd, .NET 5b5aa3ca852d, and Swift 5f00bbb2e5ca. At those revisions, fresh local generated applications passed 20/20 base, Secure-only, Blob-only, and combined artifact-consumer cells. On one host with real S3-compatible storage and SQLite, fixed ten-format graphs passed 55 upload-to-retention chains and 55 outer transaction rollbacks, including authorized complete temporary URLs and HTTP Range reads. These counts describe finite scenarios, not arbitrary graphs or all storage providers. Java and Rust were verified in separate local reports; their results are not included in the five-language counts.

Swift's independent S3 adapter passed 17/17 local real-storage tests at its current source revision, but has no permanent public package coordinate yet. Cross-machine GET, Range, expiry, and refresh were explicitly excluded from this acceptance scope and remain unverified. Same-host real storage, current authorization, complete temporary URLs, and actual signing lifetime remain required.

The source branches were pushed for review on 2026-10-31. Remote CI and independent review, immutable internal candidates, clean registry-only generated consumers, matching generator staging, actual deployed migration and rollback, and public release have not been marked complete. Use Latest Versions for currently published package coordinates; do not infer a new reference-module release from this page.