Public explanation of the repository-backed editorial source model as at 12 August 2026; it does not claim that every external change is detected instantaneously.
Plynth's repository-backed editorial source model records a source's stable identity, typed currency basis, checked date and change triggers. Each registered article declares its source IDs, allowing the publishing tooling to list dependent pages for manual review after a source change is verified. Those dates describe different facts and are not substituted with a deployment timestamp.
Direct answer
Each registered source receives a stable ID, canonical publisher URL, jurisdiction, type, status and change triggers. An article references that ID rather than copying an unconnected source note. Once an editor verifies a source change and selects its registry ID, the dependency lookup lists the registered pages that reference it for factual review.
The in-force NSW legislation collection remains the authority for current environmental planning instruments, and the NSW Planning Portal Spatial Viewer is the public source for relevant incorporated planning-map datasets.
Source currency and dependency ledger
A Plynth-authored model showing the separate facts required to make a freshness claim reviewable.
| Field | Question it answers | Example evidence | It must not imply |
|---|---|---|---|
| Source ID | Which source is this across pages and versions? | Stable registry key | That the source is current |
| Canonical URL | Where can the publisher's source be inspected? | NSW legislation or Planning Portal URL | Endorsement of Plynth |
| Effective date / vintage | When did this version or dataset apply? | Instrument commencement or dataset reference date | When Plynth checked it |
| Checked date | When did Plynth last inspect the source record? | Verification timestamp and receipt | That no later change exists |
| Change trigger | What event requires dependent content review? | Amendment, repeal, map replacement or dataset release | Instantaneous detection |
| Dependent pages | Which conclusions could be affected? | Registered article paths | That every page conclusion changed |
| Review state | Has a competent reviewer assessed the impact? | Pending, reviewed or revised | Automatic factual approval |
Effective date is not modified date
An instrument's effective date describes when its provisions apply. A page's
dateModified describes a substantive public revision to that page. A source
checkedAt date records an inspection event. Advancing all three during a
deployment would create a false freshness signal.
Change propagation
- Detect or receive a source-change signal.
- Verify the publisher, source identity and actual changed provision or data.
- List dependent pages from the shared registry.
- Have a reviewer identify affected claims within those pages.
- Revise only conclusions that the change materially affects.
- Update public modified/review dates only after that substantive review.
Limitations and failure modes
- A publisher can change a document or endpoint without a reliable machine notification.
- A consolidated current instrument can differ from the version applicable to an older application.
- Spatial datasets, written provisions and supporting guidance can update on different schedules.
- A source change can be immaterial to a page, but that decision still needs to be recorded.
- Repository-backed content requires a reviewed build and deployment before a new article can appear publicly.
Next questions
Inspect how a single answer retains its connection to the registered source, then distinguish source-backed facts from the interpretation that connects them to a proposal.