The Necessary Tangle

Release 0.22 · 5 September 2026

What changed, and what comes next

A clearer entrance to systems thinking, more ways through the early cybernetics literature, and the RedQuadrant rules ready for use elsewhere.

Try the new introductionExplore the historical collection

What you can use

An accessible place to start

The new systems-thinking introduction begins with recurring problems, follows a waiting-list example, and offers a ten-minute inquiry. It introduces the fields and gives routes into methods, reading, and communities of practice.

It is designed as the educational entrance for systemsthinking.info. Its content works without JavaScript, with readable type, keyboard links, responsive layouts, and a print treatment.

Early cybernetics, with its sources visible

The historical collection retains all 48 supplied entries from Wiener’s reading lists. You can search, filter by source section or review depth, follow atlas links, and download the catalogue.

Sean Manion, @TheUnjournaling, is credited for sharing the historical material. The original compilers, publication authors, and Systems Community of Inquiry transcriptions retain their separate credits.

The rules are preserved

The random RedQuadrant rule has been removed from the atlas header. The complete set of 256 rules remains available, including individual links and a random-rule control.

Exact texts and reusable code are ready for a discreet strip above the RedQuadrant footer, connected to the Tool Shed, and a practice aside beside the writing and library material on antlerboy.com.

What the numbers mean

The atlas now contains 719 canonical public entries, up from 635; 137 developed profiles, up from 128; 224 source records; 1,987 typed statements; and 24 journeys.

The 48 historical source rows resolve to 45 distinct works and one unidentified issue reference. Two works occur in more than one list. Four selected primary-passage reviews and one archive metadata check deepen this intake. Most of the listed works remain at bibliographic-record depth.

The Barrett–Shepard source supplies its three-page introduction and six categories, but none of the bibliography’s hundreds of entries. Those missing pages are still needed. A list described as 1956 includes a 1957 publication; that discrepancy remains visible.

The approved Systemic Evolution map retains its exact reviewed dataset and source-permission boundary. A title’s inclusion in a bibliography is recorded as a documentary connection, with no invented claim of influence.

What comes next

  1. Complete the missing source collection. Obtain the Barrett–Shepard bibliography pages, identify the unresolved Current Biography reference, and verify the short list’s date.
  2. Deepen the reading. Continue through the catalogue-only works, recording precise passages, useful distinctions, contested claims, and warranted connections. The source page shows the current review depth.
  3. Connect systemsthinking.info. Configure its HTTPS redirect to the new gateway. The destination is built; domain redirection is still outstanding.
  4. Add the rules to the receiving sites. Instructions, code, and placements are queued in the RedQuadrant update stream and the antlerboy.com update stream. Those integrations have not yet been deployed.
  5. Learn from use. Check whether newcomers can find a useful first question and follow it into the atlas. Further accessibility work should include keyboard, mobile, and assistive-technology use with actual readers.

Publication and checks

Benjamin P Taylor has authorised direct publication of requested site changes after validation. The repository instructions now reflect that, while retaining source rights, evidence distinctions, and access controls.

The release checks cover data integrity, source accounting, all 256 rule texts, new static routes, preserved map checksums, and the behaviour of the filters and rule controls. These checks do not constitute a full accessibility audit.

For the detailed evidence account and implementation handoff, see the release account and rules handoff. The deployment record identifies the version actually served.