Channels, parties, and dashboards in one place
Follow a party's whole life in the messenger-style talk shell, and check progress and settlement on the dashboard.
In development
Slime is the UI layer that renders CHOFAM Society's channels, parties, and dashboards. The Society core builds no screens, and Slime owns no data. This separation is not a convenience — it is a security boundary: even if the screen layer fails, the original data and permissions stay in the core.
The talk shell, party dashboards, and the UI Intent contract are in development.
State transitions, participant changes, and agent replies are shown distinctly.
Party progress and settlement status in one view.
What I do on screen is passed straight to the core.
When a UI owns data directly, a vulnerability in the screen layer becomes a data breach. Slime draws only what arrives through the contracted UI Intent, while storage and permission decisions always stay with the core.
Follow a party's whole life in the messenger-style talk shell, and check progress and settlement on the dashboard.
Core and screen exchange nothing outside the UI Intent contract. What data may reach the screen is written down — reviewable and controllable.
Originals and permissions stay with the core and each service. This is not a constraint on features — it is a safeguard that keeps a screen-layer incident from becoming a data incident.
Separating rendering from judgement keeps the screen light and the data safe.
Take the UI Intents the core sends.
Draw channels, messages, and dashboards.
Messages are written; transitions are proposed.
Actions go to the core; the core makes the decisions.
Ask us about Slime's progress and collaboration.