Skip to content
JTforMEFAMILIES · PUBLIC SERVICE · ACCOUNTABILITY
Menu

Verification / Publication method

Anger is not evidence. Neither is a title.

A working publication protocol: preserve originals, trace claims, test alternatives, minimize private information, invite correction and record what changed.

Use a claim ledger before writing the headline.

A claim ledger is a short record of the exact proposition being advanced. It should identify the underlying source, the author of that source, the date, the relevant passage, any conflicting evidence, and the level of certainty the material supports. That discipline should happen before a headline turns an unresolved issue into an apparent conclusion.

JTforME uses five labels: recorded communication for what a message or document says; finding for an identified decision by a competent authority; allegation for a contested assertion; analysis for an inference explained by the author; and proposal for what should change. A single article may contain all five, but they must not silently substitute for one another.

A letter from an official is primary evidence of that official’s response. It is not automatically decisive evidence of every fact it recites. An advocate’s account can be important and incomplete at the same time. The task is to state the narrowest proposition the source actually supports.

Preserve originals and distinguish every derivative.

Keep native emails, original attachments and their timestamps in the private working record. Link forwards and copied chains to their originals so they are not counted as independent events. An automated receipt, a human review, a return and a corrected filing are different events even when Gmail places them in one conversation.

Create public editions separately. Record what was removed and why: contact data, repeated signatures, family identifiers, privileged material, or unrelated messages. Do not label a typed extract as an original. A file checksum detects byte changes; it does not authenticate testimony or certify that a document’s statements are true.

The current source register is an initial subset, not evidence that this process has already been applied to every historical site asset. The claim-review worksheet makes the review reproducible for the next addition.

Read past the first satisfying sentence.

For a support complaint, read through the resolution. For a refusal, read the scope of the request and the cited basis. For a disclosure, check what was actually produced rather than equating an acknowledgment with completion. For a family-service dispute, distinguish provider availability from a confirmed appointment, participation from benefit, and inability from deliberate refusal.

The support case study includes the later envelope-status answer and the requester’s closure authorization. Those events do not erase the earlier complaint. They prevent the earlier complaint from becoming a false present-tense claim that no answer ever arrived.

Actively look for the explanation that would weaken the preferred interpretation: a different custodian, a corrected address, a necessary safeguard, a response outside the same thread, or a missing attachment. Record the search scope. “Not found in the reviewed material” is a statement about the review, not omniscience.

Publish the mechanism, not a child’s private life.

A process failure can often be explained using the responsible role, the required action, the obstacle and the eventual outcome. Avoid private diagnoses, school identifiers, appointment locations, copied child messages and home-contact details when they are not necessary to the public question.

Before release, inspect document text, visible images, metadata, download names, alt text, JSON, search snippets, cached previews and quoted email chains. A black rectangle over text is not reliable removal. De-identification must account for combinations of details that permit readers to infer a child’s identity.

Permission to review correspondence is not a blanket assertion that every item may safely be published. Attorney-client, protected court and clinical materials require separate review. Uncertainty about a sensitive item should stop its public release, not be hidden in a disclaimer.

Give an answer somewhere to land.

For a specific institutional criticism, frame the response request around the disputed fact or measurable outcome. Ask which statement is wrong, which record supports the correction, and what happened after notice. Do not ask someone to prove loyalty to the author’s interpretation.

Keep receipt, substantive response and remedy separate. A reply may be incomplete but still relevant. A correction should state the previous proposition, the corrected proposition, the source and the date. Preserve necessary history without continuing to amplify a superseded claim as current.

Requests for correction use the existing site channel; this release creates no new private-case intake. Do not send a child’s unredacted records to make a general publishing correction.

A publication gate, not a ceremonial checklist.

GateRelease questionStop condition
SourceCan a reviewer locate the supporting item and relevant context?Only a recollection is available but the draft calls it documentary fact.
Contrary evidenceDoes the account include relevant later answers or corrections?The narrative ends before a known substantive response.
AuthorityAre current rules separated from proposals and opinions?A preferred reform is described as an existing legal entitlement.
PrivacyAre identifying details necessary and safe to publish?The explanation can work without the child’s private information.
Reader valueCan the reader take a useful, appropriate next step?The page repeats condemnation but supplies no source or usable route.
Technical qualityDo links, mobile layout and downloads work as shipped?The package or site cannot reproduce the published claim.

Automated text checks do not replace legal, clinical or privacy judgment. AI-assisted drafting and code can help organize work; they do not independently corroborate a source. This release does not claim professional legal or clinical clearance.

Keep the context with the claim.

Share the page, not a cropped conclusion. This page is free without an account.

R44 / Practical pathway · November 9, 2026

Legal-authority checks are scoped, not a blanket certification.

R44 links each new family-law pathway to its supporting official authority and identifies the date checked. The machine-readable authority map states which new pages use each source. It is not a claim that all older guides were rechecked or that an attorney approved the website.

Fictional examples and organizational tests are identified separately. A planning tool never turns the user’s selected topic into a legal eligibility finding.

Support children. Account for the burden. / November 9, 2026

R45 separates legal rules from bookkeeping and proposed measures.

The R45 authority map identifies sources supporting the new pages. Household arithmetic is tested with fictional examples. No review of a private support case, complete historical-guide verification or independent professional clearance is claimed.