The standards

Every rule we hold ourselves to, in the words the code uses.

Not a summary. Each section below is generated from the register the product actually enforces, so a rule cannot be softened for a reader without being softened for the machine at the same moment.

What is published here

Every rule this organisation holds itself to, and the two things deliberately absent from the list.

why

A rule nobody can read is not a rule. It is a decision made about somebody, communicated to them only at the moment it is applied.

published

/api/standards/community: The community standard itself: the five-step ladder, what is NOT actionable, and the eight things removed without a ladder at all -- each saying why the ladder does not apply.
/api/standards/the-feed: How the feed works: the eight reactions and why a thumbs-down is safe here, what a repost may carry, and why the river ends.
/api/standards/roles: The six roles somebody can pick at sign-up, and the ask attached to each. The ask is the whole point.
/api/standards/enforcement: What earns a warning, what earns a ban, how long each lasts, and the list of things that are NEVER a violation.
/api/standards/moderation: What happens after you report something -- which lane it goes into, who reviews it, and what the outcomes are.
/api/standards/corrections: The right of reply: unconditional, answered inside five days, and the five things that may never happen to it.
/api/standards/what-we-will-not-build: The converse of every absolute, and the feature the founder asked for that this project refused, with the reasons.
/api/standards/who-this-is-for: Who Outpost serves, with numbers -- including the ones that are currently zero.
/api/standards/your-guardian: The four agents, what each watches for, and how one is assigned.

not here

counts: How many accounts have been sanctioned, how many reports filed. That is the transparency report, a different surface with a different question behind it. Mixing a tally into a page about the rules invites reading the tally as the rule's justification.
your own record: What sanctions you carry is yours and lives behind authentication. This router does not know who is asking and does not need to.

The community standard

What is actionable, what is never actionable, and the ladder a person climbs before anything permanent happens.

the ladder

steps

warning
freeze_3_days
freeze_7_days
freeze_30_days
banned

each step

step
warning
offence
0
freeze days
0
when
First time a post calls for people to unite to commit violence against a group of people.
action
The post is removed. The person is told which post, which rule, and what happens next time — in a sentence, not a citation.
appeal
Reply to the notice. A human reads it.
step
freeze_3_days
offence
1
freeze days
3
when
First offence after the warning.
action
The account cannot post, message or list for three days. It is not deleted, nothing they wrote elsewhere is removed, and the notice states the date and hour it lifts.
appeal
Reply to the notice. A human reads it.
step
freeze_7_days
offence
2
freeze days
7
when
Second offence within the same rolling year.
action
Seven days. Nothing is deleted. The notice states what the third offence costs, so nobody arrives at thirty days surprised.
appeal
Reply to the notice. A human reads it.
step
freeze_30_days
offence
3
freeze days
30
when
Third offence within the same rolling year.
action
Thirty days. Nothing is deleted. The notice states plainly that a fourth offence in the same year ends the account.
appeal
Reply to the notice. A human reads it.
step
banned
offence
4
freeze days
not measured — this is a null, not a zero
when
Fourth offence within the same rolling year.
action
The account and its email are banned. A person makes this call and their name is on it — the ladder brings the account here, it does not close the door by itself.
appeal
The decision says who made it and how to reach them. A ban is the one sanction that must be reviewable by somebody who did not impose it.

the count resets

window: rolling 365 days from each offence
why: A permanent record turns one bad week in 2027 into a ban in 2031, which is not moderation, it is bookkeeping with a grudge. The count that matters is the pattern happening NOW. An offence older than a year is history and history does not stack.
what does not reset: The hard-removal list below. Those are not offences on a ladder and there is no count to age out.

not actionable

examples: Offensive, prejudiced or hateful opinion that calls for no action.
Removing people for views the moderators dislike turns a civic commons into a taste committee, and the founder's ruling is explicit: hate speech alone is not grounds for termination. It may still be replied to, argued with, or ignored. It is not removed on that basis.
why: An opinion that calls for no action is not moderated here, however disagreeable. The alternative is removing people for views the moderators dislike.

removed without a ladder

The enforcement ladder

Five rungs, the durations attached to each, and the way back. A human confirms every flag.

never a violation

categories: beachwear
bikini
crude
directed_profanity
insult
insults
light_clothing
lingerie_clothed
name_calling
profanity
rudeness
shirtless
swearing
swimwear
underwear_clothed
vulgarity
what this means: Reports in these categories are dismissed automatically and cannot be flagged. Rudeness is not a rule violation here. Being disagreed with sharply is not a rule violation here.

the ladder

steps

warning
comment_restriction
group_restriction
temp_ban
permanent_ban

in order

Each step is more than the last. Nothing skips ahead except the categories named below as immediate.

default durations in days

comment restriction: 7
group restriction: 30
temp ban: 14

the ones that are bans

permanent_ban
temp_ban

strikes

ban length by strike count

3: 14
4: 30
5: 90

permanent at

how to read this

A strike is recorded only after a human confirms the flag. The count is yours alone and nobody else can see it.

How a report is handled

What can be reported, the two lanes that work differently, and what a report passes through before anybody decides.

what can be reported

comment
message
post
user

If we get something wrong about you

The right of reply, the five things we will never do to a correction, and the permanent ledger.

if we get something wrong about you

you may always reply: yes
answered within days: 5
what may never happen to your reply: delete
deny
refuse
reject
suppress
why that list exists: assert_reply_not_refused() raises on every one of them. It is not a policy somebody could quietly stop following; it is a function call that fails.

the ledger

corrections are permanent: yes
how that is enforced: delete() exists only to fail loudly, so no code path can quietly erase the record of having been wrong. A later correction may supersede an earlier one; the earlier one stays forever.
the ledger is readable and empty: The ledger is at /report-an-error and holds no entries. The page says which of the two readings that is -- nothing has been reported yet. The intake went live on 2026-08-29; a zero from before that date proved nothing, and this one starts meaning something now. A blank table would have said the other reading by omission: that we have never been wrong.

the states a reply passes through

submitted
acknowledged
answered

How the feed works

The eight reactions, the repost ladder, what happens to your words when somebody deletes the post above them.

the eight reactions

reactions

key
agree
glyph
👍
means
I agree
note
Agreement with what was said. Not applause, not approval of the person.
key
disagree
glyph
👎
means
I disagree
note
Disagreement with what was said. It moves nothing and hides nothing — there is no ranking for it to feed.
key
care
glyph
🫶
means
I care about this
note
For a neighbour having a hard time. The one that matters most on a local board and the one most products leave out.
key
strength
glyph
💪
means
Stay strong
note
Encouragement to keep going, for somebody in the middle of something hard rather than at the end of it.
key
celebrate
glyph
🙌
means
Good news
note
Something worked. A win, however small.
key
gratitude
glyph
🙏
means
Thank you
note
Gratitude for something done, or a request made in earnest.
key
solidarity
glyph
✊
means
I stand with this
note
Solidarity. Distinct from agreement — you can stand with somebody whose argument you would put differently.
key
respect
glyph
🫡
means
Respect / acknowledged
note
Received and respected. The civic version of a nod, and the right response to a post you do not intend to argue with.

one per person

yes

what you see

to everyone: The distinct reactions present, and WHO gave them — 'Maria, James and four neighbours'. Never a total, and never a per-reaction tally.
to the author: Their own post's counts, because the person who wrote it is entitled to know how it landed. This is the only place a number appears.
why not public counts: A public tally is a leaderboard whether or not it sorts anything, and a leaderboard creates the incentive by itself: people start writing for the number. Showing who reacted is warmer and it is also the version that cannot be gamed, because a name is accountable and a number is not.

why a thumbs down is safe here

There is no path from a reaction to placement. The feed is chronological, so disagreement cannot bury a post -- it can only be visible beside it. On a ranked feed the same button is a downvote; here it is an answer.

never built

reaction leaderboards: Most-reacted anything is a ranking with a friendly name, and it is the exact mechanism this product refuses.
reactions as a sort key: There is no path from a reaction to a position in the feed. Recency and round-robin are the only arrangements and both are facts about the post.
notifying on every reaction: A notification for each thumb is an engagement loop wearing a courtesy. Reactions are collected and shown when the author looks.
reaction history on a profile: A public list of everything a person has ever agreed with is a political dossier assembled by accident.
inferring interest from reactions: The one thing the founder ruled out entirely: no data is ever collected based on posts, and that includes reactions to them.

reposting

kinds

repost: The original, forwarded under your name, with its author attached and visible. Never silently re-attributed — the byline stays theirs and yours is added, never substituted.
quote: Your words, carrying the original inside them. A new post that owns its own visibility setting, which still may not exceed the original's.
save: Private, to you. Not a repost — it creates nothing anybody else can see. It is on this list because it is what a lot of people actually mean when they press share, and giving it its own control stops 'save for later' from becoming accidental amplification.

visibility may only narrow

order: public
local
private
why: A post written to a neighbourhood was written to a neighbourhood. If a stranger can lift it to the open internet, the author's setting was never a setting.

never built

widening visibility: A post written to a neighbourhood was written to a neighbourhood. If a stranger can lift it to the open internet, the author's setting was never a setting.
reposting a private post: Private means the author only. There is no chain of consent that starts with somebody who was never shown the thing.
repost counts as ranking: Most-reposted is a trending list, which is the mechanism this product refuses. Reposts are not counted into any ordering.
silent reattribution: The original byline stays. A repost adds a name, it never replaces one, and there is no display in which the reposter appears as the author.
keeping a copy after deletion: A person who withdraws what they said has withdrawn it. Keeping it alive under someone else's name decides that their deletion was a request rather than an instruction.
auto reposting: Nothing is ever reposted on a person's behalf, by a schedule, a suggestion, or a default. Every repost is one deliberate act.

how it lays itself out

in one line

one column, whole posts, visible chains, and an end

a post is whole

no truncation under the limit: If it was short enough to write, it is short enough to show.
collapse is the readers choice: Very long posts may be collapsed WITH a control the reader operates. A collapse the reader cannot undo is truncation wearing a hat.
media does not autoplay: Already refused next door. Restated because a video in a river is exactly where autoplay creeps back in.
no detail page requirement: A permalink exists so a post can be linked to. Nothing about reading the feed should require visiting it.

chains

narrowest link wins: A chain is exactly as visible as its least visible link. Reposting may narrow and never widen (repost_core), so a chain that passed through 'local' is local from there down, forever.
every link keeps its author: original_author_id survives each hop. A byline is never replaced by the person who passed it along.
private authors are named not linked: Someone whose profile is private still appears in the chain by the display name they chose -- because an unattributed link is a rumour -- but the name is not a door into a profile they closed.
no editing upstream: A repost may add below. It may never alter a link above it. The quote-mangling that ruined reblogs elsewhere is a data-model problem, and it is solved by not allowing the write.

the end of the feed

message: You are caught up.
why: The river ends because there is genuinely nothing new, and saying so is more respectful than pretending otherwise.
what is not shown here: No 'while you were away', no resurfaced older posts, no suggested accounts. An honest end is the whole feature.

taken from tumblr

single column: One river down the middle. Not a grid, not two columns, not a masonry wall. A grid asks the eye to choose which post to look at first, and that choice is a ranking the reader makes without meaning to. A column has no first-among-equals.
whole posts in the stream: A post appears in full where it sits. No truncation into a card, no 'read more' on an ordinary-length post, no separate detail page you must open to see the thing you were already looking at. The card pattern exists to raise the click-through rate on a page that counts clicks. Nothing here counts clicks.
chains are readable inline: When somebody reposts with a comment, the original and every addition are stacked in the body, attributed, oldest at the top. The argument is the post. Hiding it behind a number is how a conversation becomes a scoreboard.
mixed media one stream: Text, photo, quote, link, video -- all in the same river. Splitting media into tabs makes people post the kind that gets the best placement, and then the placement is writing the posts.
reverse chronological: Newest first. Already how feed_composition_core.arrange works; naming it here because it is also the thing people mean when they say they miss the old dashboard.
low chrome: The post is the interface. Metadata furniture -- counters, badges, chevrons, promotional rails -- is absent rather than merely small.

left behind on purpose

infinite scroll: Refused in feed_composition_core with its own reason. Civic Style loads the next page when the reader asks for it and then stops.
public note counts: Tumblr shows a note count. reactions_core shows WHO, not how many, and hands raw counts only to the author of the post. A public counter is a leaderboard with one contestant.
endless recommendation rail: 'Posts you might like' between the posts you actually asked for requires a model of the reader, which is the one thing ruled out.
chain length as status: A long chain is not a good post; it is a post that travelled. Nothing in the arrangement reads chain length.

when something you quoted is deleted

shown where the quoted body was: The original post was deleted.
why not silently remove it: A quote with its quoted half simply gone reads as though the quoter wrote something that does not make sense. The tombstone is what keeps their words legible.
what it must not say: Never the deleted text, never a cached copy, never who deleted it or when. A withdrawal that leaves the words behind in a grey box was not a withdrawal.

who can delete your words

decided: yes
ruled on: 2026-08-29
by: the founder
in one line: Your words die with your post. Other people's words do not.
under the post you delete: Gone. They were written under that post and that post was the context. comments.post_id is ON DELETE CASCADE and always was.
under a quote of it: Untouched. A quote is a separate post carrying the quoter's own words, and the comments were written under the quote. It gains a tombstone where the quoted body was -- the context preserved rather than changed.
under a bare repost of it: Untouched, and the repost becomes a tombstone instead of being deleted. A bare repost carries none of the reposter's writing, so Option B removes it with its source -- but once somebody has commented under it, deleting it would destroy writing belonging to neither the reposter nor the original author.
when the quoter deletes their own quote: Its comments go. That is the 'unless' in the ruling: the person deleting is the person whose post it is.
reactions are not counted: A reaction is a mark, not writing, and the ruling says 'the comments of others'. A bare repost with fourteen reactions and no comments still goes. If that is wrong it is a separate decision, and it should be made on purpose rather than inherited from this one.
applied in: 20260829_a_repost_that_carries_somebodys_words_becomes_a_tombstone.sql
verified live: All four cases proved as data against production on 2026-08-29: a comment on the deleted post gone; a quote surviving, tombstoned, with its comment intact; a silent bare repost gone; a commented-under bare repost surviving, tombstoned, with its comment intact.
why this is on the page: Because a person deciding whether to write something under somebody else's post is deciding whether it can be taken away by a stranger. On most platforms it can, and nobody says so.

the ruling behind all of it

Founder, 2026-08-29: 'THE UI IS STRICKLY TO REFLECT THE STYLE, NOT THE ALGORITHM, SCROLL JUNK, KEEP THE RULE.'

Who this is for

Named populations rather than a market. The zeros on this list are real and are left visible.

one sentence: Outpost teaches civic literacy — complicated government and legal processes rewritten in plain language so everyday citizens can understand and use them, building reading and comprehension along the way — delivered through the local organizations that already teach them.
channels: 5
populations: 5
design choices traced: 7
ring 1: Chicago North Side — Rogers Park, Edgewater, Uptown (Wards 48/49/40). The organization's own address. Walkable, one library system, one alderman's office, and a population that matches every served group below.
people served: 0
organizations using it: 0
honestly: Zero. Nothing is deployed to a public frontend yet, no organization has been approached, and no person has used any of this. Every population above is who Outpost is BUILT for, evidenced by public statistics about them — not a claim about anybody it has helped. No grant application, sponsorship deck or partnership email may state or imply otherwise until this number moves and somebody can name how it was counted.
why the zeros are here: A served number is the figure most worth inflating and the one easiest to inflate without lying -- 'reach', 'audience', 'impressions'. The count published here is people served, and while it is zero it says zero.

The six roles

What each person can do here, and why every one of them carries an ask rather than a rank.

roles

key
educator
label
Teacher or educator
who
Classroom teacher, professor, homeschool guide, tutor.
ask
ask
Use one Outpost page in one lesson, and tell us what broke.
why you
You are the only person on this list who will find the wrong reading level, the missing definition and the page that assumes something a fourteen-year-old does not know. We cannot find those from here.
first step
Open the branch you teach next. Read one page as your class would.
what you get
Every page free forever, no account required for students, and nothing collected from a minor.
key
parent
label
Parent or guardian
who
Parent or guardian of a learner.
ask
ask
Look up who represents your household, and show one of them to your kid.
why you
Civic knowledge moves through households more reliably than through classrooms, and a parent who can name their own representative changes what their child assumes is knowable.
first step
Enter your address. Read your House member's most recent recorded vote.
what you get
A dashboard of what your learner has read, and control over their data.
key
librarian
label
Librarian
who
Public, school, or academic library staff.
ask
ask
Put one Outpost page on a reference desk answer, and tell us what people actually asked.
why you
You run the last free building in most towns, you already answer civic questions all day with no budget for it, and nobody builds for you. The questions your patrons ask are the questions this project should be answering and we do not have that list.
first step
Look up your own district. Ask whether it would have answered yesterday's question.
what you get
Free, printable, source-cited pages with no login wall and no tracking.
key
student
label
Student
who
A learner of any age. A minor's role is set with guardian consent.
ask
ask
Find one thing your own representative actually did, and check the source yourself.
why you
The habit this project is really trying to build is following a claim back to its document. It is a skill, it is learnable, and it is best learned on a fact about someone who represents you.
first step
Open one vote. Click the source link. Read the actual bill text.
what you get
Everything free, and nothing collected from you if you are under 13.
key
activist
label
Organiser or activist
who
Anyone already organising in their community.
ask
ask
Bring one meeting date and one document to your local group's record.
why you
You already show up. What you usually lack is the receipt — the roll call, the filing, the agenda, the thing that turns an argument into a citation. We have those and you have the room.
first step
Find your ward or precinct. Add the next public meeting on its calendar.
what you get
The record, sourced and dated, free — and a group bounded by the geography you actually share a decision with.
key
none
label
None of these — just me
who
A person. That is enough and it is not a lesser answer.
ask
ask
Look up one thing about your own government that you did not know this morning.
why you
Most people never do this once. Not from apathy — because nobody ever showed them it takes ninety seconds and costs nothing.
first step
Enter your address. Read who represents you.
what you get
No account needed, no tracking, no ask for money on that page.

local leader

key: local_leader
label: I organise things where I live
prompt: Do you already bring people together locally — a block club, a mutual aid group, a PTA, a congregation, a union local, a market, a team? Tell us. We will not publish it without your say-so.
ask: Say what you already run, and where. Nothing gets published until you approve it.
why them: Every durable local network in the record was carried by a small number of people who were already doing the work before the software existed. Finding them is worth more than any launch.
we give: First access to your area's group, help setting it up, and the record for your own patch.
never alone: No group opens with one organiser. A second person holds the keys before it is visible to anybody, there is a written way to hand them over, and going quiet is a stated state — 'quiet since June' — not a failure and not a deletion.

note

This is your own answer about where you fit. It is not a permission, it changes nothing about what you may see, and you can change or clear it any time.

count

why each has an ask

A role is a claim about who somebody is. An ask is what we do with the claim, and a role with no ask is a form field.

no campaign vocabulary

yes

why that matters

These asks are addressed to educators, parents and librarians on behalf of a 501(c)(3) applicant. Language borrowed from a campaign would make an ask for help read as an ask for support.

Your Guardian

Four agents, how one is assigned, and how to tell which is yours.

agents

name
GABRIEL
title
The Herald
creed
No lie passes me unseen.
watches
phishing links, scams, impersonators, and fraud aimed at you
sigil
📯
color
#E3B83A
name
METATRON
title
The Scribe
creed
Nothing done in shadow escapes the record.
watches
bot swarms, spam floods, and coordinated manipulation
sigil
📜
color
#7E6BB0
name
MICHAEL
title
The Shield
creed
No gate I hold is broken.
watches
break-in attempts, stolen sessions, and attacks on your account
sigil
🛡️
color
#9E2B3A
name
RAPHAEL
title
The Healer
creed
What is wounded, I make whole.
watches
over your recovery, your appeals, and setting things right
sigil
🕊️
color
#4FAE72

how one is assigned

Deterministically, from your account. The same member always gets the same Guardian -- it is not reassigned, and it is not random each time you look.

which one is yours

Not answered on this route. It needs to know who is asking, and no member can see theirs anywhere yet. Filed as a debt in surfaced_core.OWED against guardian_core.

What we will not build

Absolutes, each with its converse stated, and the only route by which one of them could ever change.

the absolutes and their converses

id
a-person-is-not-a-record
we are
We publish what governments and institutions did.
we are not
We will not build a profile of an ordinary person, store what they said verbatim, tie a count to an identity, or impute a crime to anybody who has not been convicted of one.
id
children-are-a-floor-not-a-market
we are
The age ladder starts at four, and a kids surface is held to a stricter standard than anything else here.
we are not
No account, no data collection, no third-party code, no advertising, no wagering, no competition surface, and no feature that would cost us the kids routes to keep.
id
machines-gather-humans-assert
we are
A machine may collect, format and propose. Only a named person may assert that something is true.
we are not
No process here signs for a human, approves its own work, or certifies a fact. Not even under deadline, and not even when it is obviously right.
id
non-partisan
we are
The record is the same regardless of who it is about.
we are not
We will not host party material, endorse a candidate, run political advertising, or route money to any campaign — including one we agree with.
id
the-facts-are-never-the-perk
we are
Process, earliness, voice, credit and access may be gated.
we are not
Facts, sources, corrections and every educational surface never are. There is no tier that buys a truer answer.
id
we-do-not-exploit-attention
we are
Nothing here is ordered by, priced on, or designed around how much attention it captures.
we are not
No engagement ranking, no streaks, no infinite scroll, no notification designed to pull somebody back, no wager, and no leaderboard of people.
id
we-say-what-we-cannot-show
we are
Every surface states the limits of its own data with the same weight it gives the data.
we are not
We will not imply a completeness we do not have, and we will not let a gap go unmentioned because mentioning it weakens the page.
id
who-we-are
we are
A civic-education organisation. Everything Outpost publishes exists so somebody can check a thing about their own government themselves.
we are not
We are not a news outlet, not a campaign, not an advocacy group, and not a party. We do not tell people what to conclude.

a feature that was asked for and refused

what

Betting and prediction markets across the app.

the refusal

no stake: Nothing of value is risked. No money, no credits, no tokens, no in-app currency of any kind.
no prize: Nothing of value is won. Not cash, not product access, not a badge that unlocks anything.
no house: Outpost never offers odds, never takes a position, and never has an interest in an outcome. It records what you said and what happened.
no leaderboard: No ranking against other people. A leaderboard reintroduces the compulsion loop through the back door, and the person you are competing with here is your past self.

why it is published

A refusal a reader can see is worth more than one only the code knows. It is also checkable: forecast_core's gates fail the build if a stake, a prize, or a route reachable by a child appears in it.

how an absolute changes

By a human ratifying an amendment. air_core raises MachineCannotRatify if anything else tries.

How we keep our own teaching current

The cadence every claim is re-checked on, the topics watched, and the five edits this job will never make.

what this is

Everything Outpost teaches carries a source and a date it was last checked. This is the schedule on which we check it again.

cadences

class
agency_guidance
recheck days
180
why
Program eligibility, forms, and process pages are revised often and quietly.
class
case_law
recheck days
1095
why
A holding can be narrowed or overruled. Three years is a compromise between churn and staleness.
class
constitutional_text
recheck days
3650
why
The text of the Constitution changes roughly once a generation. The 27th Amendment was the last, in 1992.
class
directory
recheck days
365
why
Who holds an office and how to reach them turns over with elections and reorganisations.
class
explainer
recheck days
365
why
A third party's account of a primary source. The law under it may not move for a generation while the page around it is rewritten, relinked, or quietly retired. Added 2026-08-30 on two readings from the same week: the National Constitution Center's Interactive Constitution moved off its old path and left a 404, and archives.gov/electoral-college still described the 2024 cycle with a 2023 review date and no mention of the Electoral Count Reform Act. Both were classed by their HOST as constitutional_text, which is a 3,650-day cadence, because the host also publishes the actual text. The text is not the talk about the text.
class
pedagogy
recheck days
730
why
Standards frameworks (C3, NGSS, CCSS, CASEL) are revised on multi-year cycles.
class
regulation
recheck days
180
why
Agency rules change on a rulemaking calendar, published in the Federal Register.
class
statistic
recheck days
180
why
Published statistics are superseded on a release schedule; an old number is a wrong number.
class
statute
recheck days
365
why
Statutory numbers (thresholds, wage floors, seat counts) move with legislation.

topics we watch

accessibility
digital-skills
elections-administration
federal-structure
founding-texts
government-transparency
learners
legislative-process
levels-of-government
media-literacy
personal-finance
public-finance
reading
rights
success-evidence

this job never

A stale claim is never silently re-dated. Writing last_verified is an assertion that a human went and looked; a machine writing it is a lie with a timestamp on it.
A claim's text is never rewritten by this job. If the world changed, a person decides what we now teach.
A source_url is never swapped for a working one. A source that moved is a finding, and the finding is the point.
A unit is never unpublished automatically because a claim went stale. Removing material from children mid-course is a bigger act than leaving a dated citation in place, and it is a human's to make.
A cadence is never widened because something is inconveniently overdue. The schedule may only be changed deliberately, in the watchlist, by a person who says why.

who acts

The Radar produces a queue. A person works it. No claim is re-dated, rewritten, re-sourced or withdrawn by a machine.

What the Radar cannot tell you

The limits of the check, stated by the thing doing the checking.

the radar cannot tell you: Whether a claim is TRUE. The Radar knows when a claim was last checked and by what cadence -- never whether the source still says what we say it says. Only a person reading the source knows that.
Whether a source is trustworthy. An unmatched host gets flagged for classification, not for quality.
Whether the curriculum teaches the right things. Coverage gaps are measured against the watchlist we wrote, so a subject nobody thought of is invisible to both.
Whether a feed said anything. The Radar knows a feed is due; the reading is a human act and its result is whatever the human recorded.
Whether a 'no_change' check really happened. Recording an outcome is an assertion by the person who recorded it, exactly like last_verified. The Radar keeps the assertion and its author; it cannot audit it.
this job never: A stale claim is never silently re-dated. Writing last_verified is an assertion that a human went and looked; a machine writing it is a lie with a timestamp on it.
A claim's text is never rewritten by this job. If the world changed, a person decides what we now teach.
A source_url is never swapped for a working one. A source that moved is a finding, and the finding is the point.
A unit is never unpublished automatically because a claim went stale. Removing material from children mid-course is a bigger act than leaving a dated citation in place, and it is a human's to make.
A cadence is never widened because something is inconveniently overdue. The schedule may only be changed deliberately, in the watchlist, by a person who says why.

What is deliberately not on this page

Two things are measured when you ask for them, and a copy of either frozen into this page would be a claim about a moment that has passed.

/api/status: It decides at request time whether a dependency answered, and its whole position is that UNKNOWN IS NOT OPERATIONAL. A snapshot of a probe is a claim about a moment that has passed.
/api/transparency: Counts read from live ledgers, publishing null where no ledger could be read. A frozen null is indistinguishable from a frozen zero six weeks later.
/api/education-radar/queue: The tally of our own overdue claims. Founder-gated, and live.

Live, both of them: /status and /transparency.

Served by the API from the same functions: /api/standards · /api/education-radar/policy · /api/status · /api/transparency. What money buys here is at /disclosure; where we stand on every governance document is at /governance.