Ownership and guarantees

This page defines ownership boundaries, modification rights, and the guarantees associated with libraries generated using Hydra Forge.

These boundaries are intentional. They exist to provide clarity, protect long-term maintainability, and ensure a clean separation between the generated system and the engine that produces it.

Ownership of delivered libraries

Clients fully own the libraries generated using Hydra Forge.

• All project-specific Python source code
• All native source code written for the project
• All compiled native artifacts
• All documentation and test suites

Clients may use, modify, redistribute, and maintain this code independently, with no technical dependency on Hydra Forge for runtime operation.

Hydra Forge engine: ownership and transparency

Hydra Forge is a proprietary engineering engine owned by its author.

The engine is delivered alongside the generated library for execution, inspection, and verification.

All Hydra Forge engine components are provided as plain-text source files. There are no compiled binaries, encrypted payloads, or black-box components.

Engine operations — including environment creation, native compilation, verification, documentation generation, and diagnostics — are implemented using readable, inspectable scripts.

Libraries are generated using an internal factory system that is not delivered, licensed, or embedded in client repositories.

Clients receive the generated system and a transparent engine execution layer. Ownership of the engine itself is not transferred.

Use and modification of the engine

Clients may use the embedded Hydra Forge engine as delivered, subject to contractual terms.

Inspection of engine code is inherent to delivery.

Modifications to the engine do not transfer ownership and shift responsibility for correctness, maintenance, and verification to the modifying party.

Scope of guarantees

Hydra Forge guarantees apply to libraries generated and verified using the unmodified engine and preserved structural invariants.

• Structural integrity of the generated project
• Correct native integration
• Accurate, reproducible documentation
• Deterministic verification behavior

Guarantees are explicit: if the engine or enforced structure is modified, guarantees no longer apply automatically.

Collaboration and engine evolution

Clients interested in extending or improving Hydra Forge are encouraged to collaborate.

Improvements may be incorporated into the engine by agreement, with ownership of Hydra Forge retained by its author.

This model enables shared progress without fragmenting the engine or weakening its guarantees.

Verification context

Verification reflects the state of the system at the time it is executed.

Successful verification asserts compliance with Hydra Forge invariants at that specific point in time.

Summary

Hydra Forge delivers complete, client-owned libraries generated by a proprietary, fully transparent engineering engine designed for long-term maintainability.

Clients own their libraries. The Hydra Forge engine remains owned by its author.

This model balances transparency, enforceable guarantees, and long-term architectural integrity.