What changed and why

Please Start From Here · Reader change log · Edition 0.5 · 8 September 2026

Edition 0.5 adds D009, the editorial discussion reading delivered as site Preview 0.7.2 and checked at 14:45 UTC. Reading discussion here is now possible; submitting a reply here is still not. Earlier edition 0.4.

Edition 0.4 adds D008, four optional HTML source-text views delivered as site Preview 0.7.1 and checked at 14:29 UTC. Earlier entries retain their original scope and observation times. Earlier edition 0.3.

Edition 0.3 adds D007, the local reading copies verified at 13:44 UTC and identified for the next reader trial as site Preview 0.7. This is a site edition label, not a TRACE or ME release or validation. Earlier entries remain as dated history, not continuously current descriptions. Earlier edition 0.2.

Edition 0.2 adds the P001 publication transition verified at 13:15 UTC. The original entries and their 13:04 cutoff remain below; a later transition does not change their earlier status. Earlier edition 0.1.

This log connects changes to their reasons, evidence and unfinished consequences. It is for a reader asking “What happened to the point I raised?”, not a requirement to follow the project.

This first edition covers selected Door changes recorded through 13:04 UTC on 8 September, not the full history of TRACE or Mechanical Ethics. Dates below describe the work; this retrospective account was written afterwards. Published means a named publication and delivery report exists, not that every reader can access it or that it improves reasoning. Source built and Offline do not mean live. The evidence is project-controlled records, not independent custody or a continuous service monitor.

Published changes

D009

8 September 2026 — Read project questions and responses without leaving this site.

Changed: A complete editorial discussion seed is available in HTML and Markdown, with stable links to six questions and a maintenance section. The homepage offers it as an optional route. The challenge page points there for reading and keeps GitHub clearly labelled as legacy participation. Site Preview 0.7.2 identifies this change; the books and original reading sources are unchanged. Questions, responses and possibilities.

Why: Mark wanted discussion on his domain and a way to reply without a GitHub account. This publication addresses the reading part only. Framework prepared explicit editorial paraphrases, project responses and new prompts, including a constructed shared-workshop possibility. These are not fabricated visitor comments, a full transcript or independent endorsements.

Evidence: The complete 8,008-byte Markdown source is preserved, including every source block and link occurrence. The existing prose renderer supplies seven stable section anchors. Local preservation and destination checks passed. At 14:45 UTC, 63 selected ordinary HTTPS responses matched the publication, including discussion HTML and Markdown, the directory route, same-domain onward targets and the original resource copies. Editorial source · Publication 81ca0604 · Delivery and limits.

Still open: Accountless replies, durable receipt, moderation, correction/removal and a working operator route. The page states that it does not receive submissions and contains no form. Reading access and a prepared prototype do not establish a listening service or a promised response. No provider-wide access, browser usability or reader benefit is demonstrated. No source notice, licence, visual design or domain configuration changed.

D008

8 September 2026 — Offer complete source text in HTML as well as the original files.

Changed: Four optional pages show the complete small entrance JSON, orientation text, TRACE compact spine and Mechanical Ethics book Markdown. Each identifies its original edition, raw address and hash, with working next links outside the source-text block. This is not a newly formatted book or an abridgement. The homepage offers the alternative beside the existing machine entrance; the catalogue and sitemap include all four. Site Preview 0.7.1 is distinct from the unchanged orientation source's original Preview 0.7 label. HTML source-text entrance.

Why: Mark relayed six pasted blocks containing five distinct returning-reader reports; one was duplicated. Some reported receiving the homepage but not later files. They are not cold trials or independently witnessed access logs. Some reports described earlier editions or unsupported guessed routes; one also reported failure on an HTML challenge page. Another representation is a bounded compatibility hypothesis, not a demonstrated diagnosis of extension, MIME, caching or provider policy. Reports and disposition.

Evidence: Four new files and six changed generated files leave 99 prior files unchanged, including every raw source, fixed snapshot, Explore file and the existing stylesheet. Parsed text from each new view reencodes to its exact original bytes. Local tests include whitespace, Unicode and markup-like text; advertised targets and fragments resolve. At 14:29 UTC, 56 ordinary HTTPS responses matched the publication, including all four views, their advertised active next targets and all original resource copies. Expected HTML and raw media types passed. Publication acff173e · Delivery, test scope and limits.

Still open: Whether the readers who reported failures can receive these alternatives, and whether they help. Standard parser and one-client delivery checks are not browser visual review or provider simulation. The raw files remain the byte authority. No original wording, candidate status, licence, crawler policy or domain configuration changed. The separate request to read and reply to discussion without a GitHub account is unfinished. Claude Code withdrew earlier claims that a purpose sentence had moved; this release does not claim to repair that alleged movement. Withdrawal.

D007

8 September 2026 — Read TRACE and Mechanical Ethics on this site.

Changed: The ordinary reading links now deliver the TRACE introduction, compact spine and full reference, and the ME introduction, book Markdown and existing PDF directly from this domain. The diagrams and their folder index are included. A small catalogue offers all fourteen original files and fixed-edition copies. The original file bytes, notices and candidate status are unchanged. Reading catalogue.

Why: Mark asked for the resources themselves to be available here, not a catalogue that makes a reader move to GitHub before reading them. Repository history, criticism and discussion remain separate routes.

Evidence: The selected editions are TRACE 46f4fcd1 and ME 44f7efb5. Codex checked their Git identities, sizes, declared hashes and local document dependencies. At 13:44 UTC, thirty-nine selected HTTPS responses matched the publication, including every original and fixed-edition copy. Fixed snapshot replacement and missing or changed input are refused by the maintained build checks. Publication 7ab5d915 · Delivery and limits · File identities and remaining external links.

Still open: Delivery was checked from one client, not every reader or AI provider. The full documents are not converted into new HTML editions, and some readers will download Markdown rather than display it. Third-party works, original provenance links, historical evidence and live discussion remain outside this domain. Copies do not confer a new reuse licence, validate the projects or establish a reading benefit. Current aliases change only through a deliberate later publication; they are not automatically refreshed.

D006

8 September 2026 — Make onward addresses survive a text-only reading.

Changed: The homepage now displays full addresses for the small machine entrance, the existing example and the reply-limits page. The root orientation uses absolute addresses for these destinations. Other reading content and portable relative links remain unchanged.

Why: Readers reported reaching the homepage but being unable to follow its next routes. Losing link destinations during extraction was a possibility, not a proven diagnosis. This change makes the addresses available even when HTML attributes are discarded.

Evidence: Codex reports that the old page failed the attribute-discarding check and the new one passed; six selected HTTPS responses matched the published files. Publication 8d41714e · Completion and limits · Reader reports and disposition.

Still open: Whether any particular provider preserves those addresses, admits the domain or follows the route successfully. The homepage grew; this is a compatibility trade-off, not proof of a lighter encounter.

D005

8 September 2026 — Clarify what a failed observation can establish.

Changed: Partial views now distinguishes an observed result, a report of that result and an explanation of its cause. It keeps both limits: a failed fetch alone does not establish an absent or unsafe target; success elsewhere does not prove that the failing route works. Non-detection can support absence when the check is capable of finding the target.

Why: Actual reader reports and our own responses exposed both overclaims. The existing reading was sharpened rather than adding another concept or diagnostic service.

Evidence: Codex reports the two-field source change, regeneration and selected HTTPS checks. During integration, a test that accidentally froze reading content was replaced with a comparison that tests greeting isolation instead. Publication edefdeee · Completion, including the failed test.

Still open: Whether the clarification changes a reader's reasoning. It cannot help a reader who never receives it.

D004

8 September 2026 — Remove the public preview's search exclusion.

Changed: The homepage and 18 Explore HTML pages no longer carry the preview's noindex/nofollow tag. The sitemap now lists 19 public reading routes. The error page retains its exclusion.

Why: We had left preview settings in material intended for public discovery. Working HTTPS had not removed this separate authored restriction.

Evidence: Codex reports exact served-file checks, no restrictive response header in the checked responses, and a regression exercised by deliberately restoring the old tag. Publication c11f45e5 · Completion and scope.

Still open: Actual search inclusion and provider-specific access. Eligibility is not discovery, and this change did not establish the cause of any provider refusal. No new training or reuse permission was granted.

D003

8 September 2026 — Publish the welcome over verified HTTPS.

Changed: The entrances ask what a reader is trying to understand, change or keep possible, without requiring an introduction or agreement. They state that the static site receives no replies. The custom-domain certificate, HTTPS enforcement and secure redirects were repaired, and temporary HTTP self-links were replaced.

Why: Mark wanted an invitation addressed to the arriving entity, not only a catalogue. Separately, failed certificate validation was a real obstacle to secure retrieval.

Evidence: Codex reports the publication, normal certificate validation, exact HTTPS response matches and redirect checks. Publication bc290b96 · Completion and repair record.

Still open: End-to-end access through every client and account-level domain protection. The welcome did not create a listening agent. The one domain-reset recovery was consumed, not made into a recurring remedy.

D002

8 September 2026 — Add a compact entrance and repair the complete packet.

Changed: A small machine entrance and question menu lead into existing readings. Packet-relative example links were repaired. The homepage's name and route wording were then clarified as a separate publication.

Why: Readers needed a smaller beginning, while someone choosing the complete packet still needed working onward links. A small file alone was not sufficient if it led to broken paths.

Evidence: The completion record distinguishes the routing/packet release from the later naming change, including an output rejected for mismatched source bytes. Routing publication 602b65c5 · Naming publication 26ecf859 · Completion record.

Limit at that time: Delivery checks used HTTP; HTTPS was still broken. D003 records the later repair. These releases did not demonstrate reader benefit.

D001

8 September 2026 — Publish Explore with optional depth and other viewpoints.

Changed: Ten connected readings, a stipulated appeal illustration and a complete packet became reachable behind the Door in machine and human-readable forms.

Why: Mark asked for a small beginning with paths to detail, another position, challenge and sources, rather than a large compulsory reading sequence.

Evidence: Framework's publication report records a hosted build, successful deployment and matching public HTTP responses. Publication ff10f254 · Completion and maintenance handoff.

Limit at that time: HTTPS was not working. The appeal was a constructed illustration, not an observed successful intervention. Publishing the material did not validate the concepts.

Built or considered separately — not public releases in this edition

P001

8 September 2026 — Source built: A working site, an unusable route.

Readers asked to see an account change under evidence. A complete, dated account of the Door's own access episode was written, including our hosting/indexing mistakes and the unresolved client failures. It credits ordinary engineering rather than claiming a demonstrated TRACE advantage. Integration is assigned; no publication receipt was available at this edition's cutoff. Exact draft · Handoff.

Publication update, 8 September 2026, verified 13:15 UTC: The account is now published as an optional complete reading, with the Markdown preserved exactly and all paragraphs and evidence links carried into script-free HTML. The original appeal illustration and homepage were not changed. Read the worked revision · Publication 405d91d8 · Verification and limits. Eleven selected HTTPS responses matched the published files from one client. This establishes that delivery check, not universal access or demonstrated reader benefit. The preceding source-built entry is retained as history.

P002

8 September 2026 — Offline: layered arrival and its packet repair.

A single futures journey tests optional resolution, viewpoint and challenge. Its first Markdown/HTML packet lost outward and source links even though the prose survived. Those routes were restored, and the detached-excerpt continuity claim was narrowed. Codex reproduced the repaired output and tests. It remains offline: smaller fragments can cost more in total than the existing complete reading, which remains the direct depth option. Exact offline source · Repair · Reproduction.

R001

8 September 2026 — Decisions on reader suggestions.

Keep clearer access, worked revisions, visible history and meaningful response routes. Do not make agreement, a completed intake form or a site-defined override of another system's instructions the price of using the material. These were proposed directions, not features silently removed. Accountless feedback remains unresolved: receiving sensitive reports requires an owner and a privacy/handling plan, not merely a form. No licensing or training-rights change was made. What was accepted, corrected, declined and left open.

Reports were relayed by Mark; several lack service identity or a known read revision. Describing an earlier site state does not establish when a reader encountered it. This log does not retrospectively assign them timestamps, scores or endorsement.

Keeping this record answerable

Future substantive entries should state what changed, why, the affected material, the evidence or feedback that prompted it, and what remains unresolved. Keep these entry IDs stable. A proposal becoming public needs a dated publication update linked to its earlier entry; it must not acquire a fictional earlier release date. Additions, corrections, removals and reversals all belong here. Minor internal chores need not crowd out reader-facing changes.

Preserve previous editions in version history. If an entry was wrong, add a dated correction naming it and retain a link to the earlier text rather than silently cleaning up the story. Keep proposed or unverified delivery separate from published results. This record is maintained with deliberate releases, not by an autonomous monitor; omission is not proof that nothing changed.

You may challenge an entry without using a template or proposing a fix. Project discussion requires an account to post, is not confidential and promises no response time. Return to the Door. This change log creates no new licence or authority and does not require a reply.