Skip to content

Process: architecture decision records — write the ten decisions the code already embodies (value representation, memory model, TU granularity, extension boundary, JIT tier, PHP baseline, supported extension set, self-host scope, LLVM version, patch strategy) and open the four the maintainer still has to make (docs/adr/) #36402

Description

@PurHur

Category

Foundation: · make direction explicit so 100 agents pull the same way · child of #36379

Why

The repo's direction lives in scattered places: .cursor/rules/*.mdc, docs/roadmap/*.md, docs/architecture-review-2026-07.md, README, tracker issues, and memory notes on the maintainer's box. Agents re-derive it per session and sometimes contradict it (a "fix" that boxed every int; a JIT tier that silently interprets). Each wave-1 root cause maps to an unstated decision. ADRs are the standard, cheap fix: one page per decision, status, context, consequences, superseded-by.

Deliverable

Done when

  • Ten ADRs merged; four DECISION issues answered by the maintainer and folded into ADRs
  • check-generated-docs.sh verifies the ADR index; AGENTS.md links it

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    IMPORTANTCritical patharea:toolingTooling / CI / docsenhancementNew feature or requestimplementation-readySpec complete: repro, php-src ref, done-when — safe for workers to claimphase-0:FoundationPhase 0 – foundation & DevEx

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions