A view is one concept, over one primitive

Answers Topology · Epistemology

A view is a purposeful projection of the graph: declared patterns, all asked from one kind, drawn in the way the law's own vocabulary for drawing declares, belonging to a declared deliverable where it belongs to one, and answered by binding those patterns from one row. What a view starts from and what it touches are read off its patterns and appear nowhere else. A view no row answers is not published.

What goes wrong without it

There were three names for one idea and the noise was the cost of it. A question was a path over relationships, a job was a set of those from one term, and a plan view was a hand-kept list of kinds with no path behind it at all. The hand-kept one drifted exactly as a hand-kept list does: the Journeys tab promised a recommended campaign purpose and a primary KPI per journey state, and nothing in the model reaches either from a journey state. A list that is derived cannot make that claim, because there is nowhere to write it down.

What proves it — 1

Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.

• Every view binds declared patterns from one kindViews compose
  Every view names declared patterns, all asked from one kind, drawn in a way the law's pattern vocabulary declares, belonging to a declared deliverable, a table as one of its tabs and a job as work that produces it; and some row of that kind answers at least one of them. What a view touches is derived from its patterns, never listed beside them.

Derived from — 2

• Grüninger and Fox, IJCAI-95 Workshop on Basic Ontological Issues in Knowledge Sharing, 1995Methodology for the Design and Evaluation of Ontologies
• Christensen, Hall, Dillon and Duncan, Harvard Business Review, September 2016Know Your Customers' Jobs to Be Done

Where this model stands

registry/views.json declares each: its name, the deliverable it belongs to where it belongs to one, how it is drawn, the patterns it binds in reading order, what it shows, the work it does in a reader's words, what the reader is holding, and what they leave with.

law.json `views` is the closed vocabulary of ways one may be drawn, defined once and named by the schema through values_from, as the claim classes and the evidence classes are: `table` reads across every row of its starting kind on one page, `path` reads from one row with a page for each.

The build binds each pattern from every row of the starting kind and publishes an answer only where a row fills every role, so a page exists exactly where the work can be done and says which part it cannot answer.

The four tabs of the Measurement Plan compose the seven paths they had always described in prose, declared as patterns so the plan is bound rather than asserted; FND-028 holds every view to declared patterns asked from one kind.

What it does not claim

A view binds patterns from one kind only. Work that crosses two starting kinds would need a step before the patterns begin, and nothing yet needs one.

A journey's machine-readable twin is not a view. Its roles are declared in the kernel, and a second governance for one thing is the duplication this removes; if a third way of drawing one ever earns a place in the vocabulary, that is where it would be argued.

The words a reader might type for a view are not declared, so nothing matches free text to one; they are found by reading, not by asking.

RUL-038