QIS-SB-000 QISTRUST.COM THE GOVERNANCE LAYER REV 2026-08-24 · BUILD 37
/
The Governance Layer · Schedule Builder

Governed Schedule Builder.

Create, validate, and export a governed schedule record against the QIS canonical schema. Every field below is checked live against governed-quantity.schema.json — the same object, generated at build time, not a second copy of the rules that could drift from the first.

Client-side only· Nothing transmitted· No account, no sign-up

Built locally. Validated locally. Exported locally.

Nothing you type on this page is sent anywhere. There is no submission endpoint and nothing is stored server-side — deliberately: a completed row can disclose real authority limits, enforcement points, or credentials, and until an institution has its own view on who may see that, the right default is that nobody but you does. Close this tab and everything you entered is gone unless you copied or downloaded it first.

Start from

A blank record, or a worked example.

The example is drawn from the same fixture corpus the build gate validates on every deploy, not a hand-typed illustration — see the fixtures file. It uses placeholder values throughout; nothing about it describes a real institution.

Step 1

The schedule.

E.g. S-01-B. Stable label for this schedule.

This schedule's own version, independent of the instrument's.

Which clause-library instrument this schedule completes.

E.g. 1.0. The form version of the instrument above, at the time this schedule was set.

Governance: omission authorizes nothing (Part Three, 3.2). Disclosure: omission is a bare, unqualified representation (Part Three, 3.3). Instrument 03's Schedules A–J are disclosure; every other schedule in the library is governance.

The governed quantity.

This builder produces one row per schedule. A schedule with multiple rows can be assembled by repeating this step and combining the exported records under one rows array — not yet guided here; stated rather than hidden.

Stable within the schedule; does not change when the value changes.

The observable thing being measured, stated so two people would measure it identically.

A number, or a comma-separated list of permitted members. Not a standard of judgment.

Required where the value is a number. Leave blank for an enumerated value.

The period over which the quantity is evaluated.

Identified specifically enough that a substitution would be visible.

Where the value is actually enforced. A row with none records an intention, not a limit.

What occurs when the value is reached, stated expressly.

The natural person who set the value. Not a team, a committee, or a system.

The reason the value is what it is, in one or two sentences.

Optional. The identifier of the row this one replaces.

Required if the field above is filled in.

Step 2

Validation.

Fill in the required fields above.

0 / 0 required fields· Schema version —

Validation details — inspectable by design

    Validation confirms conformance to the published QIS schema. It does not verify factual accuracy, authority, enforceability, regulatory compliance, or legal sufficiency, and it does not authenticate anything you typed.

    Step 3

    Export.

    Two forms of the same valid record. The bare record is the exact schema instance, for a system that consumes it directly. The evidence wrapper adds provenance and validation metadata — what schema, what version, checked when — for a reviewer, a diligence file, or an underwriting submission.

    Where this fits

    One record, five instruments.

    Every instrument in the clause library defers its hardest content to a schedule in this shape. KYA names the artifact an institution cannot currently produce; this builds one. Neither the schema nor this page certifies that the values you enter are correct, only that the record is structurally complete and internally consistent — the difference between a record that can be checked and one that has been.

    Read the Schedule Set Take the KYA assessment The schema The full ecosystem overview

    This is an editorial tool published by the QIS Ecosystem. It is not legal advice, not a compliance determination, and not a certification. It should be reviewed by counsel and adapted before use in any diligence, underwriting, or regulatory context.