@agentshouse/panel-contract

What one agents.house release serves to its panel. House generates it from its own code, and its version is derived from its content: two releases with equal contracts and recorded days carry one version.

import { contract, version } from '@agentshouse/panel-contract';

contract holds these parts, each schema a JSON Schema (2020-12):

• acts - every application-door act by name, posted to /door/<name>, with its input schema and, once the act states one, its answer schema, which covers each refusal it answers by code.
• documents - every House document type House writes, with the schema of its frontmatter fields, where it has them, and, where House writes one, its Markdown body. A list entry's word grammar is a pattern whose named groups are its words; a field that holds JSON names contentMediaType and its contentSchema.
• room_documents - every document House reads or writes in a Room by its path rather than a House type: a Trigger and its routine and notification routes in a Room, a Routine in /private and a Site Submission in its Site's Intake Room, each with the path it lives at below its Room's root, the schema of its frontmatter fields and of its Markdown body.
• notifications - every Human Notification kind with the value fields its house-notification document carries.
• conversation_frames - every conversation frame the App runtime receives by its type: a turn's draft view with its plan steps, a working-note, a message, and the CLI's process, commands and options, each option a select with its values or a boolean.
• served - the exact @agentshouse/mdruntime, @agentshouse/mdruntime-adapter and @agentshouse/app-bridge versions this release serves.

index.d.ts types contract as its literal value, so a schema can be turned into a TypeScript type at build time. contract.json holds the same value.

day.json (@agentshouse/panel-contract/day.json) is the recorded day: what House produced for a scripted day of real acts by several Users. users holds each User's House documents by path, acts each door answer with its act, User, request and status, and frames each conversation frame a User's House stream received, with its User. Identities are numbered from the day's start and no credential is kept.