Current progress
A working pilot with a defined evidence path.
Current maturity is presented honestly alongside evidence limitations.
- Pilot phones
- 10
- Dashboard
- Functional
- Assurance
- Pending
Current position
W.O.L.F has a recorded pilot baseline. This is a position statement for evaluation, not a deployment or approval claim.
Implemented baseline
Communications and collaboration. Recorded pilot capability includes messaging, controlled file collaboration and common-operating-picture integration subject to release review.
Device lifecycle. Device register, revoke support, repeatable rebuild and Guardian check-in are recorded in the current baseline.
Oversight. A functional dashboard supports approved project records and assurance-oriented review.
Private access. The public narrative recognises a private service boundary without exposing topology or configuration.
Laboratory evidence and its boundary
Controlled Android laboratory evidence is limited in scope. It can demonstrate that an agreed action was observed in a controlled setting; it is not proof of operational effectiveness, independent assurance, formal approval or an authority decision.
- Documentary
- Limited technical proof
- Controlled validation
- Independent evidence
- Authority decision
| Evidence category | What it supports | What it does not support |
|---|---|---|
| Documentary baseline | Recorded project position | Independent confirmation |
| Limited technical proof | Controlled observed behaviour | Operational release |
| Future independent evidence | Assurance decision input | Automatic authorisation |
In development
Guardian management boundaries, assurance evidence, security testing, controlled evaluation and the first three KURs remain in development. Each needs owner review, traceability and proportionate validation before it can support a stronger claim.
Planned work
Future work includes W.O.L.F Sustain, recovery and monitoring improvements, controlled trials, multi-project development and independent testing. These are evidence-led intentions, not dated delivery commitments.
Decision path
- Confirm requirement owner and evaluation scope.
- Collect controlled evidence against the KURs.
- Review assurance gaps and dependencies.
- Seek appropriate authority decisions for any future release.