One type, one dashboard in a .gram document · r1

Archived revision r1, recorded 2026-10-14T07:58:14.272Z by portal-reference-finalize. Current page: Document views and the shared record vocabulary.

One type, one dashboard

A .gram file remains the canonical source. Core 2.0.1 selects one dashboard for its declared type and returns ResolvedView/1. The client renders that result; it does not choose another ViewSpec or invent a screen.

Declare the document type

Declaration	Dashboard
`schedule@1`	Journal
`project@1`	Project Tracker
`knowledge@1`	Knowledge

Write the template declaration on the document, for example template project@1. The dashboard is not a separate document and selecting a type does not duplicate the source. Templates govern field formats, cardinality, required fields and typed action targets; ordinary unknown fields remain preserved.

Missing and invalid declarations

When no template is declared, Core selects the first eligible recommendation, falling back to Project Tracker when none is eligible. That recommended dashboard is read-only. The original document can still be edited through the normal authorized document editor.

An unknown id/version or malformed declaration has no dashboard. Show the document and Core diagnostics without guessing another type, rewriting metadata or creating an empty dashboard.

One document dashboard and one folder home

There are no screen tabs, sidebar screen lists, ViewSpec switchers or search/filter/sort/group query toolbar. A folder opens one home screen from WorkspaceView/1. Document and dashboard are two representations of the same source, not a choice of several dashboard templates.

Author with the template contract

Use Core templates to inspect the type, fields, allowed values, typed actions and AI authoring profile. Use template-check to diagnose proposed governed writes before patching. Create a document with the chosen type; execute typed actions through the approved write path. Do not derive completion from history or invent absent dates, status, ownership or operational health.

schedule@1

Declare template schedule@1. Event requires t and at; end is exclusive and must have the same date/time form as at. Date-only events are all-day; datetime without end is a point. Task requires t and x. Use start and due, not scheduled. No recurrence expansion: write individual occurrences. Example: V review
t Weekly review
at 2026-10-13T10:00:00+09:00
end 2026-10-13T11:00:00+09:00
x confirmed. Use templates and template-check before patch; never derive done from history.

project@1

Declare template project@1. Every record needs t. Use task x backlog/open/active/review/blocked/waiting/completed/cancelled/archived. Use start/due for planned dates, done only for an explicit completion date, rank for manual order, owner for a person id or name. Add subtasks with a part-of link to the parent. Keep estimate as raw text. Example: T design
t Design the drawer
x active
p high
start 2026-10-13
due 2026-10-16. Use templates and template-check before writing; preserve unknown fields.

knowledge@1

Declare template knowledge@1. All known records require t. Use source ref for a URI or asset path; preserve it as text. Decision x is proposed/accepted/rejected/superseded. Events require explicit at. Example: K outcome
t Recovery outcome
d Audit confirmed restored state. Cite source/evidence links rather than asserting live health. Place knowledge/source/decision/evidence in the body and event separately. Use templates and template-check; keep metadata and unknown fields intact.

Keep time and evidence explicit

recorded_at selects the persisted revision known at that point; as_of evaluates effective-date logic within that revision. History commit time is not an event or completion date. Missing dates and unsupported evidence remain unknown; an empty component is not proof that work is done or a service is healthy.

Scope

The current dashboard contract is extracted from Core source and exercised against the same Core API. Historical pages retain their earlier source. The separate MCP reference retains its explicitly dated development capture and is not a claim that the newest Desktop/Cloud tools have been recaptured.

Source and renderer evidence

Canonical source SHA-256: dd469c194d96bf48d4ab911acc91ec5f4f07f9f0c4ca34cf1a0fa17b68cfbb6c
Selected revision: r1 · sha256:73e934356bcc004ea87288b18002b945e8d285d89239d85857d7fdf69f332175
Local renderer: configured local Thegram renderer · API thegram-web-render/1
Core source: git+https://github.com/clab-one/thegram-format.git?rev=b16489e1d0d77d38f82d2f61776524737aa31557#b16489e1d0d77d38f82d2f61776524737aa31557

Canonical source: 1.gram