At a high level, the platform treats worker execution, result ingestion, and result access as separate concerns so that trust can be enforced in layers.Documentation Index
Fetch the complete documentation index at: https://webscraping.titannet.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Core trust principles
Identity before execution
Workers identify themselves to the platform before they receive or submit work. This allows the control plane to associate runtime activity with a node or device identity.Controlled result intake
Workers do not publish results directly to end users. Output is returned through platform ingestion paths that validate and normalize what the worker has produced.Platform-managed media access
Media is not exposed as raw storage access. Users retrieve media through Titan-managed URLs tied to execution ownership and download policy.Separation of public and internal concerns
Task creation and result access are public platform concerns. Scheduling, ingestion, and worker coordination are internal platform concerns. Keeping these separated reduces accidental coupling and keeps the public API stable.Browser node trust model
For browser nodes, trust is built around:- Node bootstrap and registration
- Explicit runtime capability advertisement
- Controlled work assignment
- Managed template loading and verification
- Ingestion-based completion
Chrome extension trust model
For extension workers, trust is built around:- Device registration
- Authenticated backend connectivity
- Platform verification for task eligibility
- Controlled script delivery
- Server-side receipt of task reports