Coverage and evidence

Scope

Primary analysis scope: the five supplied files under docs/ltp_trees/, treated as one provisional Second Renaissance causal model.

Supporting implementation scope: the Project LTP skill contract, model schema, local-dashboard source, server, tests, fixture, README.md, MOTIVATION.md, and PLAN.md. These files determine how the supplied trees are normalized and rendered; they are not evidence that the Second Renaissance group behaves as described.

Analysis mode: reconciliation. The documents already contain a Goal Tree, Current Reality Tree, conflict diagrams, Future Reality Tree, and Prerequisite Tree. This run reconciles them into one stable-ID model and infers the missing Transition Tree.

Inventory and coverage

AreaDiscoveredExaminedTreatment
docs/ltp_trees/*.md5 files / 2,561 lines5Read in full and normalized
Project LTP instructions/references/schema77Read in full
Dashboard behavior and server/test contract10 key files10Read directly
Project intent and plan4 key files4Read directly
Primary repository inventory106 files before these deliverablesClassifiedNot claimed as full-project behavioral analysis

The repository inventory excluded .git, the secondary .claude worktree, and installed node_modules. Generated dashboard bundles, package locks, browser-demo exports, .DS_Store, thumbnails, screenshots, build metadata, bytecode, and backup *.md~ files were classified rather than read as primary evidence. Large theory documents outside docs/ltp_trees were not treated as source evidence for this model. The cited but absent Second Renaissance whitepapers and “How” paper were not examined.

Evidence map

IDSource linesObservationEvidential use
EVD-1Goal Tree 1–24Explicit goal and eight CSFsProvisional destination
EVD-2CRT 5–13System boundary and candidate throughputBoundary and goal unit
EVD-3CRT 17–51Fifteen named UDEsCandidate present effects
EVD-4CRT 55–81Six candidate root causesCandidate causal structure
EVD-5CRT 291–317Conversion architecture named likely constraintConstraint hypothesis
EVD-6CRT 321–346Lived validation explicitly requiredEarliest validation gap
EVD-7Conflict 496–524Movement/depth cloud and core injectionCentral conflict
EVD-8FRT 17–39Tree stewardship protocolGovernance injection
EVD-9FRT 41–68Throughput, conversion, layered participationPrincipal injections
EVD-10FRT 72–113Learning, stewardship, pockets, replication, reviewOperating-system injections
EVD-11FRT 522–629Five negative branches and trimsRisk controls
EVD-12PRT 80–112Consent-based entry prerequisitesEntry objective
EVD-13PRT 126–160Recurring practice and safetyPractice objective
EVD-14PRT 173–215Contribution and stewardship safeguardsLeadership objective
EVD-15PRT 219–275Dense containers, sangha, outward servicePocket objective
EVD-16PRT 278–322Maturity-rated replicationReplication objective
EVD-17PRT 329–372Movement tied to pocket learningScaling sequence
EVD-18PRT 452–482Governance-first dependency chain; TT missingTransition ordering
EVD-19PLAN 29–58Dashboard only verified on toy fixtureRendering context

Evidence limits

The primary documents are authored analysis, not operational observations. The CRT calls itself provisional and asks the group to validate its UDEs and arrows. Accordingly:

  • Explicit document content is observed as artifact evidence.
  • Claims about actual group behavior remain provisional.
  • Proposed causal links and future effects remain inferred or provisional.
  • No entity is marked confirmed because no group decision or user confirmation of the substantive model was supplied.
  • No throughput.yaml was created because no real period observations exist.
Built with LogoFlowershow