Pakkawork

Disclaimer · Reliance boundary

Disclaimer

Last updated · 11 September 2026

Pakkawork adds an enforceable control and evidence layer between AI agents and provider APIs. It reduces specific operational risks; it does not eliminate every risk or replace the judgement, authority, security programme, or legal review of the people operating the system.

What the service can—and cannot—assure

Service boundaries in full

7 sections
What the service can—and cannot—assure · 01

1. Software and evidence, not professional advice

Pakkawork is software. Product pages, control mappings, ledger records, examples, and documentation are technical information, not legal, regulatory, security, accounting, or other professional advice.

What the service can—and cannot—assure · 02

2. Controls do not guarantee a safe outcome

Server-side policy, approval, host containment, verification, and recovery reduce defined risks but cannot guarantee that every authorised action is wise, every provider behaves correctly, every credential remains secure, or every harmful effect can be reversed.

Workspace administrators, operators, and approvers remain responsible for configuration, authority, context, and decisions made through their workspace.

What the service can—and cannot—assure · 03

3. Verification coverage is explicit

Twenty-two published contracts perform real post-condition read-back. The other 533 generated contracts execute and meter without independent outcome confirmation. A generated contract must not be represented as verified merely because the provider returned a successful status.

What the service can—and cannot—assure · 04

4. Human approval has limits

An approval records a human decision on the request presented. It does not prove that the approver had complete context, authority outside Pakkawork, or knowledge of every downstream consequence. Critical quorum requires two distinct people but does not replace organisational review procedures.

What the service can—and cannot—assure · 05

5. Third-party providers

Connected APIs, identity systems, infrastructure, and analytics services have separate availability, quotas, security, and terms. Pakkawork does not control their outages, response accuracy, policy changes, data practices, or account restrictions and is not endorsed by them.

What the service can—and cannot—assure · 06

6. Evidence mapping is not certification

Pakkawork can map live control evidence to the EU AI Act, NIST AI RMF, and ISO/IEC 42001. A mapping is not a legal-compliance determination, audit opinion, attestation, or certification of Pakkawork or a customer organisation.

What the service can—and cannot—assure · 07

7. Product facts and external references

Live product counts refer to the implementation state identified by Pakkawork and may change as contracts and providers evolve. Roadmap scale is labelled as roadmap rather than current availability.

External standards, specifications, provider names, and third-party sources remain the property and responsibility of their publishers. Reference to them does not imply sponsorship or endorsement.