Search all guides
Documentation / Operations
From local tests to operational acceptance
Passing simulations is a useful milestone, not proof of live connectivity or financial correctness.
Run the local contracts
The public repository includes module activation, lifecycle, ownership, security and compatibility contracts, BYOT and emergency suites, and operator availability, ordering, concurrency and JavaScript search tests. They use synthetic fixtures and test doubles. Run in an isolated development environment following each package README.
node examples/operator-number-search/tests/search_contract.cjs
php examples/operator-number-search/tests/ordering_contract.phpComplete real integration gates
Verify trusted customer mappings, actual form and lifecycle callbacks, receipt-origin persistence, commercial eligibility, allocation confirmation, billing recovery and shared limiting across every consumer. Multi-host protection requires a shared gateway or separately verified distributed limiter.
Browser and production acceptance
The 0.7.0-dev number-search milestone still requires genuine desktop and mobile browser acceptance, including keyboard behaviour and proxy disconnect handling. Controlled FreePBX 16/17, carrier, test-call, privacy and production acceptance remain separate gates. Website testing does not close these software acceptance requirements.
Known limitations
There is no automatic remote lifecycle delivery, inbound lifecycle listener or selective PBX teardown protocol. Public carrier and ordering fixtures are not commercial connectors. Future transport decisions are not specified; do not implement against an imagined API.
Evidence required before real service use
| Gate | A meaningful result |
|---|---|
| Browser | Actual desktop/mobile forms, keyboard selection, cancellation, paging, field isolation and proxy disconnect behaviour |
| Ordering | Callbacks reject invalid updates and checkout; immutable origins survive real order creation |
| Provisioning and billing | Confirmed matching allocation, correct reconciliation and recoverable partial outcomes |
| Carrier protection | All consumers share real request limiting, including other hosts or gateways |
| PBX acceptance | Controlled FreePBX 16/17 activation, native routes, reload and call tests |
| Emergency | Current number authority, reassignment protection and authoritative carrier confirmation |
| Operations | Protected logs, durable journals, tested backups, rollback and explicit owner approval |