chart

chart is where the Lab brings structure to what it does, and keeps it long enough to count as memory. A proposal, a decision, a task assigned and followed up: all of them write into chart, and stay there. And a meeting, a planting, an energy reading, a reflection, an event: those too. chart is multi-tenant: each Lab lives at its own subdomain and keeps its own records, separate from every other Lab’s records.

The records are not pre-defined schemas. chart holds them as opaque documents organised into collections the Lab defines for itself: proposals, decisions, memberships, contracts, agreements, tasks, anything the Lab needs to write down and find back later. Every write leaves an audit trail. Who wrote, what changed, when, and why if the writer offered a reason.

chart is not a project-management tool. The point of chart is structure, and underneath structure, memory. What was proposed, who was there, what was agreed, what was amended. A Lab that signs a contract with a municipality can retrieve that contract in five years. chart is also not a public archive; records are Lab-scoped by default. A Lab may export to lens or to the federation repository, but that is an act of the Lab, not an automatic publication. chart reads from people for who is who.

How the instruments relate

people is the floor. Identity, membership, consent. chart, compass, and lens all read from people; they do not duplicate it. A change in people propagates to all three by definition.

• interpretationlens
• registrationchart · this instrument
• orientationcompass
• relationpeople