The product is simple.
The work behind it is open to inspect.
Start with what a person does. Follow how 4789 responds. Go as deep as the protocol and code when you want proof.
01Open workflows →02Read the protocol →03See release status →
Workflows
Trace complete journeys from a shelf or list through title, source, player, and television.
Compatible service protocol
See the small manifest, catalog, metadata, stream, and subtitle contract that compatible services can use.
Public source and releases
Inspect the code, release history, checksums, issue tracker, and contribution path when the public repositories open.
Why show the machinery?
4789 connects personal libraries, third-party services, local files, and devices in the home. Clear boundaries matter.
- The interface comes first.Architecture explains a claim only after the product has made it understandable.
- Unknown stays unknown.Missing source, codec, or receiver facts are not rewritten as certainty.
- Local state stays local.No 4789 account is required. Optional connected services receive only the requests needed to do their work.
- Failures get names.Playback, network, source, and receiver errors are treated as different problems.
Begin with one evening.
The workflow map is the clearest route from the product story into the engineering behind it.
Open the workflow map- First
- Human journey
- Then
- System response
- Finally
- Protocol and code