{
  "contract": "course-content/1",
  "slug": "measuring-the-estate",
  "title": "Measuring the Estate: tally/1 and pulse/1",
  "primitive": "Measuring the estate (tally/1 and pulse/1)",
  "audience": "Anyone who publishes a number about an organization and wants a reader to believe it",
  "summary": "The core literacy of an honest organization: telling a figure you can raise at will from one you cannot. This course teaches the two formats the estate publishes its numbers through — tally/1, in which every figure declares who has to act for it to move, and pulse/1, condition over time with deltas derived rather than asserted — and the survey discipline that keeps a ratio from lying.",
  "track": "working-with-agents",
  "pin": {
    "source": "flashyos/tools/estate-tally.mjs + pulse/1",
    "state": "unverifiable"
  },
  "intro": [
    "Any figure an organization can raise simply by talking more about itself is an engineering gate, not evidence — and publishing it as if it were evidence is the most common way a trustworthy-looking dashboard misleads.",
    "The estate answers this with formats that make the distinction structural. tally/1 refuses to publish a figure that does not name who has to act for it to move. pulse/1 shows condition over time and refuses to let a caller assert a delta it did not compute. And the survey rules underneath both — ratios not counts, unread is not zero — stop a measurement from flattering itself.",
    "Five lessons. You will finish able to look at any published number and ask the one question that matters: who can move this, and did they, or did we?"
  ],
  "lessons": [
    {
      "n": "01",
      "title": "A gate you can move versus a claim you cannot",
      "outcome": "Classify any figure as an engineering gate or a witnessed claim, and know which is worth publishing.",
      "body": [
        "Every number splits into two kinds. One kind rises whenever the organization does more of its own work — entities defined, relations declared, adoption of its own standards, commits sealed. The other kind moves only when someone outside acts — a countersignature, a settlement another organization agreed to. The first is an engineering gate; the second is a claim a reader can actually trust.",
        "The estate publishes the second kind precisely because it cannot move it at will. A countersigned count that reads zero is more believable than a large number the organization could inflate by talking about itself, because the zero is one nobody would print unless they meant it.",
        "The literacy is to ask, of any figure: could we raise this without anyone else doing anything? If yes, it is a gate — useful internally, misleading in public. If no, it is worth publishing. Most dashboards mix the two without saying which is which; this course is about not doing that."
      ],
      "source": {
        "label": "Flashy Network — countersignatures (a number we cannot move)",
        "href": "https://flashynetwork.com/countersignatures/"
      }
    },
    {
      "n": "02",
      "title": "tally/1: every figure names who moves it",
      "outcome": "Read a tally that separates the figures nobody here can move from the engineering gates.",
      "body": [
        "tally/1 is a figures format with one required field per number: who has to act for it to move. A document that carries a figure with no such field does not validate — the format refuses to publish a number that will not say whose action changes it.",
        "The rendering is part of the format: the half nobody here can move is printed first, and the engineering gates are labelled as such. The renderer emits both halves or throws, because nothing else stops a presenter from showing only the flattering figures and dropping the ones that would expose them.",
        "And a tally is never derived by the property that publishes it — it is measured across the estate and sealed, so an edited figure fails the build rather than reaching a reader. A number typed onto the page is right on the day someone looked and silently wrong after; a measured, sealed one is not."
      ],
      "source": {
        "label": "Flashy Network — the tally",
        "href": "https://flashynetwork.com/tally/"
      }
    },
    {
      "n": "03",
      "title": "pulse/1: condition over time, deltas derived",
      "outcome": "Explain why a pulse never accepts an asserted delta and how a correction is made.",
      "body": [
        "pulse/1 records the condition of something over time, so a reader can ask whether this was better last week rather than trusting a single snapshot. Its central refusal: a delta — the change between two readings — may never be asserted by a caller. It is derived from the readings, because a caller who could write a delta could claim a movement nothing measured.",
        "This is the same rule the estate keeps everywhere a field could be faked: a derived figure is computed, never stored, so no one can hand-write the flattering version. The reading is the fact; the trend is arithmetic over facts.",
        "A correction to a pulse is appended, not edited — a retraction with a reason, leaving the original reading in place. The history of a measurement is itself a fact worth keeping, and quietly overwriting a bad reading destroys the one thing a time series is for."
      ],
      "source": {
        "label": "FlashyOS — pulse/1 (the protocol register)",
        "href": "https://flashyos.com/protocols"
      }
    },
    {
      "n": "04",
      "title": "Ratios, not counts; unread is not zero",
      "outcome": "Apply the two survey rules that stop a measurement from flattering itself.",
      "body": [
        "A floor stated as a count is gameable: \"at least N\" is satisfied by growing the population while the share that qualifies actually falls. So floors are ratios, never counts — a smaller read cannot vouch for the whole, and a percentage moves honestly where a total can be padded.",
        "And unread is not zero. A repository or a source that could not be read is reported by name as unread and enters no ratio — it is neither counted as passing nor as failing. A check that does not apply is skipped, not failed. A survey that reached nothing keeps the previous answer rather than announcing that the whole estate is down.",
        "These two rules are why the estate's surveys can be trusted: they refuse the two easiest ways to make a measurement look better than it is — dividing by a friendly denominator, and treating silence as a good result."
      ],
      "source": {
        "label": "FlashyOS — the estate surveys",
        "href": "https://flashyos.com/protocols"
      }
    },
    {
      "n": "05",
      "title": "Say which tree you measured",
      "outcome": "State the difference between what your checkout shows and what actually ships, and always name the ref.",
      "body": [
        "A number about \"what ships\" must be read from the branch that ships, not from your working copy. Reading a local checkout and reporting it as the estate's state is how a survey once claimed secret-scanning coverage was complete when it was less than half — and the same mistake was then made again, in a different tool, hours later.",
        "So the discipline is to say which tree you measured, every time, and to read the deployed ref when the claim is about what is live. A working tree tells you about one machine; the ref tells you about the organization.",
        "This closes the loop with the first lesson. A figure is only as honest as the two questions behind it: who can move it, and which tree did you read to get it. Answer both on the page, and the number is evidence; leave either implicit, and it is decoration with a progress bar."
      ],
      "source": {
        "label": "FlashyOS — say which branch you measured",
        "href": "https://flashyos.com/protocols"
      }
    }
  ],
  "faqs": [
    {
      "q": "Why publish a number that reads zero?",
      "a": "Because a figure you cannot move at will is the one a reader believes. A countersigned count of zero is more credible than a large number an organization could inflate by talking about itself, since the zero is one nobody would print unless they meant it. The point of tally/1 is to publish exactly the figures whose movement depends on someone else acting."
    },
    {
      "q": "What stops someone writing a flattering trend into a pulse?",
      "a": "The format refuses an asserted delta. The change between readings is derived from the readings, never stored, so no caller can claim a movement nothing measured — the same rule the estate applies to every field that could be faked. Corrections are appended as retractions with a reason, never edits, so the history of the measurement survives."
    },
    {
      "q": "Why insist on ratios and on naming unread sources?",
      "a": "Because a count floor is satisfied by padding the population, while a ratio falls honestly when the qualifying share drops. And treating an unreadable source as zero turns silence into a passing grade. Reporting unread by name, computing floors as ratios, and saying which tree you measured are the three habits that keep a survey from flattering itself."
    }
  ],
  "related": [
    {
      "label": "The Verifiable Record",
      "href": "/academy/curriculum/the-verifiable-record"
    },
    {
      "label": "The Two Tenses",
      "href": "/academy/curriculum/the-two-tenses"
    },
    {
      "label": "Machine-Readable, and Why It Matters",
      "href": "/academy/curriculum/machine-readable-and-why"
    }
  ]
}