Doctrine — the free half, in full. Read it once; it explains half of what this program does.
"Everything joins on RPUID."
PRIDE is the book GIS is geometry BUILDER is inventory ISR is condition

Four systems keep the same truth four different ways. One key ties them together, so no record ever has to be believed twice — it gets checked: against the book, on the key, every time a feed lands.

1 · The four systems of record

Each system owns one part of the truth and no other part. When two systems disagree, the disagreement is a finding — it is never settled by quietly editing one of them.

The Book

PRIDE — the register

Owns: the baseline of record — assets, uses, codes, interests.

Every other system reconciles to this one. If it is not in the book, it is not yet real — and if the ground says otherwise, the book changes on its own paper, not on a feed's say-so.

See the register's shape →

Geometry

GIS

Owns: where things are — segments, pins, perimeters.

The map proves location; it does not prove the record. A moved pin is a proposal until it is approved — and a pin never changes the book.

See the map's shape →

Inventory

BUILDER SMS

Owns: the sustainment inventory — components and condition of systems.

What a building is made of, system by system, and what shape those systems are in. It keys on the same identifier — which is what makes the tie possible at all.

Departments →

Condition

ISR

Owns: the quality and mission picture — plus the use picture.

How good the asset is and what it is actually used for. Condition and use are ISR's testimony; existence and value stay with the book.

Departments →

2 · The law of the tie

Six laws. They are not guidelines — every reconciliation this program runs is executed under them, and every difference they surface stands on one list until it is closed on paper.

  1. The RPUID is the ONLY join key. The facility number repeats across sites; names vary by style; neither joins anything. Where a human needs a composite reference, it is site + facility + RPUID.
  2. The book is the baseline. Every feed reconciles TO the book, never the other way around.
  3. Feeds produce FINDINGS, never edits. A difference is a finding. The book changes only on its own paper — a 1354, a memorandum, a data call.
  4. Captures and disposals flow book-first; the register catches up. The paper leads; the systems follow.
  5. The tie is a cadence, not an event: every extract is reconciled on arrival, and the differences stand on one list.
  6. The same law reaches every module — grants included: grant records join on the same key and reconcile to the book. No island data.

3 · Why

One priority, made mechanical

The standing priority at the top of the program is simple: all the systems of record match. Not close — match. This doctrine is that priority made mechanical: one key, one baseline, one list of differences, worked until the list is empty.

4 · How the standing reads

On the live program, this section carries a dated standing for each feed — tied, extract in hand, building to this law — with the real counts behind it, and it changes only when a reconciliation lands. The demonstration shows the shape of the standing, not the standing itself: the numbers are part of the depth, and the depth is behind the door.

FeedStanding (shape)What the live standing carries
GISTiedEach extract reconciled on arrival; the reports filed as the record set, with what the feed still owes stated on their face.
ISRTiedExistence, use, and condition compared asset by asset; past-due ratings stand as findings with an owner.
BUILDERExtract in handThe feed held, its reconciliation the remaining run — the standing says so until it lands.
GrantsBuilding to this lawGrant records joined on the key and reconciled to the book from the first record — no island data.

Doctrine page — public craft teaching, carried in full. The live standings, counts, and dates are register-derived and do not ride the public demonstration.