Inspiration
Teams exchange important files every day through ZIP archives, shared drives, email attachments, and download links. These methods can move files, but they do not provide a clear and independently verifiable answer to several basic questions:
- What exactly was delivered?
- Were any files changed, removed, or added after packaging?
- Who created the delivery?
- Is the package still identical to the original?
- Can the recipient verify it without trusting the sender's system?
This problem is especially important for small organizations, laboratories, consultants, software teams, and service providers that need reliable delivery evidence but cannot adopt a large and expensive enterprise platform.
OrbiFabric Trusted Delivery Toolkit was created to make trustworthy file delivery simple and accessible. Instead of replacing the user's files or workflow, it adds verifiable evidence around an ordinary file delivery.
What it does
OrbiFabric Trusted Delivery Toolkit contains two complementary desktop applications:
OrbiPack — Create the delivery
OrbiPack is the sender-side application. A user can select files or folders, enter delivery information, and generate a trusted delivery package in the -orbipkg.zip format.
The package contains:
- The original delivered files
- Human-readable delivery metadata
- A deterministic file manifest
- SHA-256 hashes for file integrity
- A Merkle root representing the complete file set
- Digital signature metadata
- Verification evidence
- Optional Cloud Anchor and Delivery Record receipts
The user does not need an account or a Cloud connection to create a formal local delivery package.
OrbiVerify — Verify the delivery
OrbiVerify is the recipient-side application. The recipient can drag a package into the application and independently verify it.
OrbiVerify checks:
- Package structure and required metadata
- Missing, unexpected, or modified files
- SHA-256 file hashes
- Manifest consistency
- Merkle root consistency
- Digital signature validity
- Package identity and format information
- Optional Cloud Anchor receipts
- Optional online Delivery Record status
Local integrity verification works without an OrbiFabric account or server. Cloud functionality is an optional enhancement rather than a requirement.
Together, OrbiPack and OrbiVerify create a complete workflow:
Create → Deliver → Verify → Understand
A normal ZIP archive says, "These are the files I sent."
An OrbiFabric trusted delivery package adds, "These are the exact files I sent, and you can independently verify them."
What we built during OpenAI Build Week
The core local OrbiPack and OrbiVerify applications existed before Build Week. During Build Week, the toolkit was significantly extended with a complete local-to-cloud evidence workflow.
The new work includes:
- Cloud Anchor generation from OrbiPack
- Signed Cloud Anchor receipts embedded into trusted delivery packages
- Offline Cloud Anchor receipt verification in OrbiVerify
- Delivery Record creation and verification
- One-click online verification from OrbiVerify
- Local-to-cloud verification receipt handling
- Clear separation between local verification, online verification, and verification that has not yet been requested
- Improved verification status presentation
- Additional automated tests and continuous integration coverage
These additions connect deterministic local package verification with optional online evidence while preserving the local-first design of the product.
How we built it
The desktop applications are built in Go with Wails. The interface uses web technologies while the verification engine remains in a shared Go core used by both the graphical applications and command-line tools.
OrbiPack creates the package deterministically. It normalizes package metadata, calculates hashes, creates the manifest and Merkle root, signs the evidence, and writes the final ZIP package.
OrbiVerify does not trust the stored result. It reopens the package, recalculates the evidence, compares the results, verifies signatures, and produces a structured verification conclusion.
The optional Cloud service is built with PHP, Symfony, PostgreSQL, and Docker. It can issue signed Cloud Anchor receipts, maintain Delivery Records, and respond to online verification requests.
During Build Week, Codex with GPT-5.6 was used as an engineering collaborator across the Go desktop tools and PHP Cloud service. It helped analyze the existing repositories, design the cross-application receipt workflow, implement verification logic, update the user interfaces, add tests, investigate failures, and keep the protocol behavior consistent across multiple components.
GPT-5.6 is used through Codex during development rather than as a runtime decision-maker. Package integrity and signature verification remain deterministic cryptographic operations. This is intentional: AI can accelerate development and reasoning, but it should not invent or override integrity results.
Challenges we ran into
One major challenge was maintaining consistent behavior across multiple applications and languages. OrbiPack, OrbiVerify, and the Cloud service must agree on package identifiers, canonical payloads, hash values, signature algorithms, environments, timestamps, and receipt schemas.
Small differences in JSON serialization, Base64URL encoding, field ordering, or environment configuration can invalidate a signature even when the visible data appears identical.
Another challenge was representing verification states precisely. The system must distinguish between:
- Verification passed
- Verification failed
- Verification was not requested
- Verification could not be completed
- A signing key is unknown
- Local integrity passed while an optional online check remains pending
Treating "not requested" as "failed" would mislead the user, so the user interface and result model were redesigned around explicit verification states.
We also needed to preserve the product's local-first boundary. Cloud capabilities had to add evidence without making local package creation or verification dependent on an account, license, quota, or server connection.
Accomplishments that we're proud of
We are proud that the toolkit provides a complete and understandable sender-to-recipient workflow rather than only a cryptographic library or technical proof of concept.
The recipient does not need to trust the sender's application or database. OrbiVerify recalculates the package evidence independently.
We are also proud that the Build Week work produced a complete sequence of connected capabilities:
- Generate a trusted package
- Create a signed Cloud Anchor receipt
- Embed the receipt into the package
- Verify the receipt offline
- Request an online status check
- Match the package to a Delivery Record
- Present the final result without weakening local verification
Most importantly, the toolkit remains useful when no Cloud service is available. Users can create and verify formal delivery packages locally, while organizations that need additional online evidence can enable it separately.
What we learned
We learned that trusted delivery is not only a cryptography problem. The technical evidence must also be understandable to a normal user.
A mathematically valid signature is not useful if the interface cannot explain what was verified, what was not checked, and what requires attention.
We also learned that local and Cloud verification should not be treated as competing modes. Local verification establishes package integrity and authenticity. Optional Cloud verification can add an external timestamp, current status, and shared delivery record.
Codex with GPT-5.6 was especially valuable for working across repository boundaries. It helped trace how one protocol change affected package generation, receipt signing, desktop verification, API responses, user-interface states, and automated tests.
What's next for OrbiFabric Trusted Delivery Toolkit
The next steps are to improve distribution and make the toolkit easier for real teams to evaluate.
Planned work includes:
- Signed and reproducible Windows releases
- macOS support
- Improved package comparison between versions
- Exportable human-readable verification reports
- Organization-managed trusted signing keys
- More complete Delivery Record workflows
- Private-deployment integration with OrbiFabric Pro and Enterprise
- Long-term package and file lifecycle evidence
The long-term goal is to make verifiable delivery as easy as creating and opening a ZIP file, without requiring small organizations to adopt a large centralized platform.
Log in or sign up for Devpost to join the conversation.