Execution you can inspect.
Working PHP/WebAssembly software, deployment experience, and AI tool integration.
Inspect the working runtime and define the benchmarks needed for the next application.
A working runtime provides the starting point for mission-specific validation.
Phase I plans pair a release record with a representative application.
Phase I will measure the baseline against the selected workload.
Deployment notes and test results are scoped to the proposed mission.
Review current software, planned tests, and research priorities.
Working PHP/WebAssembly software, deployment experience, and AI tool integration.
Measure startup, resource use, access boundaries, and recovery.
Test adversarial behavior, action records, and mission integrations.
Planned evidence: workload benchmark.
Planned evidence: resource profile.
Planned evidence: fault-injection test.
Planned evidence: controlled user trial.
| Dimension | Conventional PHP hosting | Containers / serverless | DESIGNA kernel |
|---|---|---|---|
| Execution portability | Environment dependent | Package and platform dependent | Validation status to be documented per target environment |
| Runtime isolation | Hosting control dependent | Runtime and platform control dependent | Current capability; validation scope defines evidence boundary |
| Resource footprint | Workload dependent | Workload and platform dependent | Benchmark pending under Phase I validation |
| Recovery controls | Operational runbook dependent | Platform and application dependent | Current recovery work; fault-injection target |
| Agent integration | Custom integration | Custom integration | Current integration capability; policy and provenance research target |
Agencies, prime contractors, universities, and small businesses can request a brief for a specific pilot or research proposal.