Beacon

Beacon — Call-Forwarding Contracts PSR-compliant contract layer for WordPress-administered call forwarding. Ships interfaces, value objects, and shared traits; an implementation plugin (e.g. Anchor) provides the concrete driver and wires everything into the shared container. Architecture - Beacon registers contracts (CallForwardingService, HttpTransport) into a PSR-11 container and fires beacon/loaded. - Anchor binds a concrete driver against those contracts on beacon/loaded. The driver fetches an HTML configuration page from the upstream PBX, parses it, and POSTs back changes to apply forwarding rules. This separation lets you swap implementations (or stand up tests with mocks) without touching consumers, and gives the same Beacon-shaped admin UI to every PBX the project ends up integrating with. Beacon ships only contracts | | | |---|---| | Beacon\Forwarding\Interfaces\CallForwardingService | The driver contract — list/save/delete rules, list targets, commit, test. | | Beacon\Forwarding\Interfaces\ForwardingException | Common throwable for driver failures. | | Beacon\Forwarding\Models\ForwardingRule | Immutable value object: match condition + target. | | Beacon\Targets\Mode