| ai_request.schema.json | A request for StellarView's AI: what arrived, the context, and the tasks asked. StellarView picks it up, runs it through Claude Code with the prompt files, and posts a result. Nothing acts on the result without a person. | 2 KB |
| ai_result.schema.json | StellarView's answer to an ai_request. Suggestions only: each waits for a person. | 3 KB |
| alert.schema.json | An alert record: one event told to people, with every send, escalation and the acknowledgement | 3 KB |
| alert_ack.schema.json | An acknowledgement: who took the alert, in what role, and when | 1 KB |
| alert_escalation.schema.json | An escalation: if nobody acknowledges in time, the next role is told | 1 KB |
| alert_route.schema.json | A route: for each role, the channel an alert goes out on | 1 KB |
| alert_rule.schema.json | An alert rule: to which roles, by which route, with which escalation. A path names it; the path decides which events. | 1 KB |
| analysis_rule.schema.json | An analysis rule: input event types, a window, a condition, an output event type. Data, never code. | 2 KB |
| asset.schema.json | An asset record: every maintained thing, a sensor included, with how each field was got | 9 KB |
| common.schema.json | Parts every Interchange message shares | 6 KB |
| document.schema.json | A document: a file that arrived, stored untouched, with its text where any could be read | 2 KB |
| event.schema.json | An event on the Interchange: one thing happened to one asset. Every listener receives it at once. | 5 KB |
| i3_event.schema.json | An event from Simplify i3 as the hub accepts it at POST /hooks/i3. The shape is the Interchange's own; how i3 sends events is to confirm (Q-35). | 1 KB |
| load_template.schema.json | A load template: the sheet a site fills in, as columns with types, rules and an example. The template is the schema. | 2 KB |
| path.schema.json | A rule path: which events it takes (by name and metadata), the policy that requires it, the action, who is told, the systems it uses and how fast | 4 KB |
| pipeline.schema.json | The pipeline as data: the order an item passes through the Collector, and the Interchange's listeners | 2 KB |
| reading.schema.json | A reading: one point's value at one time | 1 KB |
| source.schema.json | A Collector source: who sends, how it is signed, how its items are de-duplicated and classified | 7 KB |
| ticket.schema.json | A help desk ticket, to and from the desk's adapter (Jira Service Management in the support example) | 3 KB |
| trigger.schema.json | A trigger: a rule that traps an incoming reading or event and names the event it becomes. Defined, not coded. | 8 KB |
| video_source.schema.json | A video capture posted to the Collector: the meta part of a multipart upload beside the file | 1 KB |
| work_order.schema.json | A work order, to and from the CMMS. A proposed one waits for a person. | 1 KB |