Overview
How it fits together
Status: In Review
From the people who use it, through the front door and Datum Core, to the machines that run the models.
Pathways
Access
Three ways to take part
- Synod on its own. Synod and Datum Core on your own computer, with local models. Your machine is not on the model network.
- Synod on the network. Your computer runs Synod and is also enrolled on the secured model network: it can use the network's models, and can add its own.
- On the network only. A machine that only joins the secured model network to run models for it. No Synod; ours today, and in future, machines that members contribute.
Status
- Available soon
- In progress
- Planned
- Future
Access
- Members. Signed in through the portal with single sign-on.
- Private network. The secured Datum Core model network. Encrypted, with no public address: reached through the portal, or by a machine enrolled on the network.
- Your machine. Runs on your own computer and listens on that computer only.
- Public. Open to anyone on the internet.
How a request travels
A member signs in once at the Photon Datum Portal, which uses single sign-on, and opens a service from there. When you send a message in Photon Datum Chat, it goes to Datum Core, whose model gateway passes it to a model of the right size on one of the model nodes. The member services, the gateway and the model nodes sit on a secured, encrypted network with no public address: the only way in is through the portal, or by a machine that has been enrolled on the network.
The three ways to take part, A, B and C, are explained under the graphic.
Every part
| Part | Access | Status | What it does |
|---|---|---|---|
| People | |||
| Synod user | Your machine | In progress | Works in Visual Studio Code with Synod, on a computer that is not on the model network (A). |
| Member in a browser | Public | Available soon | Anyone with a membership: signs in once at the portal and reaches every member service from there. |
| Synod user on the network | Your machine | Planned | Works with Synod on a computer that is also enrolled on the secured model network (B). |
| Node host | Private network | Future | Someone who contributes a machine to the model network without using Synod on it (C). |
| Front door | |||
| Photon Datum website photondatum.space | Public | Available soon | Products, membership, services and articles. No sign-in. |
| Photon Datum Portal portal.photondatum.space | Members | Available soon | The front door to every member service. Sign in here; the portal opens each service for you. |
| Single sign-on auth.photondatum.space | Members | Available soon | One login for every member service, with GitHub, Google or GitLab. You reach it from the portal. |
| The secured model network | |||
| Datum Core | Private network | Available soon | The platform as a whole: the model gateway, agent tools, project management and search that the member services and Synod use. |
| Photon Datum Chat agent.photondatum.space | Members | Available soon | The private chat and agent workspace in your browser. Early access. |
| Git hosting git.photondatum.space | Members | Available soon | Private repositories on our own Git server, with the same sign-in. A membership service. |
| Agent tools | Private network | Planned | The actions an agent may take for you, such as reading files, searching and recording work, each checked against what your membership allows. |
| Project management | Members | In progress | Projects, tasks and decisions, with a full audit trail of every change. |
| Workspace search | Private network | Planned | Finds the relevant parts of your own documents and code, so answers are grounded in your material. |
| Knowledge Index | Members | Future | A knowledge repository in three tiers: public, protected and private. |
| Model gateway | Private network | Available soon | Sends each request to a model of the right size, on a node that has it, so a quick question does not wait on the largest model. |
| Model nodes (open-weight models) | Private network | Available soon | Our machines on the network that run the models: small and mid-sized open-weight models in four sizes, plus a model for search. They run on our hardware, not a third-party model service. |
| Contributed nodes (member machines) | Private network | Future | Machines that members enrol on the network to add model capacity. |
| A: your machine, not on the network | |||
| Synod | Your machine | In progress | The AI chat and agent panel in Visual Studio Code. |
| Datum Core (on your machine) | Your machine | Available soon | The model gateway, agent tools, project management and workspace search, running on your own computer. |
| Local models | Your machine | Available soon | The same model sizes, run on your own computer. Nothing leaves the machine. |
| B: your machine, on the network | |||
| Synod | Your machine | Planned | Synod on a computer enrolled on the model network: it can use the network's larger models as well as its own. |
| Datum Core (on your machine) | Your machine | Planned | Datum Core on your computer, connected to the network's Datum Core over the secured network. |
| Local models (can serve the network) | Your machine | Planned | The models on your computer. On the network, you can choose to make them available to the network's model gateway. |