Sitemap
Follow a branch. Open a heading to see what sits beneath it.
Numbers count the next branches shown in this map. 0 marks a leaf here, not an empty page.
SEARCH THE COLLECTION
Follow a thought.
Find an idea. Watch the route that leads to it.
A collection of possible directions
Start with a thought. Choose a match to see where it belongs.
Open any named stop on the traced route to visit its page. The light follows this sitemap’s actual parent–child links. Faint forks are neighbouring pages; numbers count immediate branches. This finds pages, not generated answers. Browse the full map below ↓
Agent welcome
Download llms.txt · Read as Markdown
A personal collection exploring how projects work. Many experiments are pre-tools: ways to discover useful framings, not finished tools for others to use. Some already support bounded tasks. Browse from curiosity, or bring a project question.
Home offers two entrances.
- Experiments: Open enquiries in four families: Composing projects, Planning and judgement, Graphs and representations, and Rethinking project work.
- Library: More established methods, bounded examples and earlier material, organised by subject.
The compact strip below the family tiles offers four alternative routes:
- All experiments: Browse enquiries and exploratory collections by their questions.
- Scenarios: Situations connected to the enquiries that use them.
- Working views: Nets, maps, matrices and screens from inside the examples.
- Compare: Explore the Gimån footbridge trials or replay the Bond Street handover from dated project evidence.
The persistent shortcuts open Experiments, Library, Scenarios and Working views. Experiments opens four family tiles; a compact link strip offers All experiments, Scenarios, Working views and Compare as alternative ways to browse the same enquiries.
An essai is a trial: a limitation or failed attempt can be useful. Each project owns its question, evidence and future direction; this guide helps you find it.
For a practical question, match the decision and mechanism before the setting. The same museum can pose an information problem or a scheduling problem; a different setting may share the mechanism you need. If nothing fits, explain the gap rather than force a recommendation.
Open the example and, where possible, try a relevant control. Separate what you observed, what the page says and what you infer. Explain what transfers to your question and what still needs evidence. Say when interaction was unavailable.
Detailed directory · Visual descriptions
Projects: questions, scenarios and limits (28)
The names, questions, scenarios and approaches follow the public project catalogue. These short boundary notes help interpret it; follow the project's own public scope when reading or continuing an enquiry. The linked End, Ways and Means statements belong to those projects.
SMC means symmetric monoidal category; WBS means work breakdown structure. Each example explains how, and how far, it uses its named methods.
| Project | Question | Scenario | Concepts | Scope, limits and sources |
|---|---|---|---|---|
| Gimmer: processes to plans | Which plans are allowed by the way the work actually happens? Explore how process rules admit or exclude plans through Petri nets, symmetric monoidal categories and WBS constructions; compare what each model preserves. | Build a small refuge halfway up a cliff. | processes, WBS, schedule | Several process-to-plan constructions share this collection. Their assumptions and coverage differ; read the chosen construction's method and checks. GitHub source (may require access) |
| Integrated risks & tasks | Can tasks and threats be understood through one process model? Treat tasks and risk events as processes competing for shared access. Compare wiring diagrams and allowable executions when either the farmer or the construction crew uses the lane. | Pour the foundations before the cows take the lane. | processes, risk, composition, category theory | Shared-resource rules expose conflicts; the model does not estimate probabilities or optimise schedules. GitHub source (may require access) |
| Project Co-design | Can a feasible finished system be delivered through acceptable stages? Six wildlife-crossing essais: compose a crossing, construct a path, compare programmes, size monitoring power, choose a common beginning and preserve evidence for later choices. | Reconnect two habitats across a busy road. | co design, trade offs, staging, category theory | Capacity and cost assumptions do not predict animal use. GitHub source (may require access) |
| Bricklaying a Rotunda | How can we explore changing project states? A collection of experiments around project dynamics, lenses and trajectories. | Build a circular brick wall, course by course. | dynamics, models, category theory | An exploratory collection of dynamics, lenses and trajectories; the chosen model's assumptions define what its paths mean. GitHub source (may require access) |
| Local to Global | When do local project views fit together? Two lines of enquiry: early Tangled Triangle sketches ask how AI interprets interfaces, topology and system architecture; later experiments test local-to-global consistency. | Fit a control centre onto the Tangled Triangle. | consistency, WBS, category theory | Early AI interpretations and later consistency checks are distinct lines of enquiry. A local-to-global result is tied to its stated model. GitHub source (may require access) |
| Shared waters: open systems | What do open-system methods help us understand about useful project chunks? Compose systems through explicit boundaries; compare organisational descriptions and test agreements about shared observations and capacity. | Connect an offshore depot, a power barge and their organisations. | open systems, composition, dynamics, category theory | First constructions of boundaries, organisations and shared observations; their computed results concern the supplied examples. GitHub source (may require access) |
| Programme Decision Sequences | How should a programme act as uncertainty unfolds? Models, worksheets, worked paths and IT decision games for acting under uncertainty. The experiments catalogue distinguishes live simulations, tutorials and historical reports. | Choose now; learn more before the next decision. | decisions, uncertainty, programmes | The collection distinguishes simulations, tutorials and historical reports. For example, its finite evidence model uses supplied payoffs. GitHub source (may require access) |
| Gimmer: higher-autonomy experiments | Can work packages share resources without hiding valid ways to build? Test what a work-package boundary must retain so shared resources and intermediate progress survive composition. Finite constructions connect Petri nets, SMCs and plans. | The same refuge, with the awkward handovers left in. | processes, WBS, higher autonomy | Exactness depends on the declared finite object and completed search. Durations do not verify construction methods. GitHub source (may require access) Public scope and method boundaries |
| Project Spines | What can schedule structure reveal beyond dates? Three essais explore the order of work, positive spine constructions and alternative groupings of concurrent work. The first retains its eight views on containment, precedence, chain exchange, schedule spines, antichain slices, finite construction, review loops, vacillation and project controls. | Build the Neidpath wall while keeping the order of work inspectable. | schedule, project controls, posets, antichains | Precedence structure and partition results do not by themselves establish a resource-feasible schedule. GitHub source (may require access) |
| Functors for Projects | How might mathematical structures illuminate project work? Browse experiments in functors, adjoints, sheaves, wiring diagrams and finite colimits, including the grounded-theory coding illustration. | Describe one project in more than one useful way. | category theory, models, project management | An exploratory collection, not one bounded foray or a complete project-management system. Each construction has its own mathematical and practical limits. GitHub source (may require access) Collection purpose and limits (3 October 2026 copy) |
| Building a Wall | Can explicit interfaces turn project work into reusable blocks? Six maintained essais explore readiness, relation algebra, repeated courses, revision forks, coherent histories and failure containment, alongside seven earlier explorations. | Build a wall that is ready to receive a roof. | wiring diagrams, composition, readiness, category theory | Readiness and interface checks concern the declared construction; they are not evidence of a completed real build. GitHub source (may require access) |
| Solway Tunnel Ontology | How can a project ontology connect to a plan? Ontology and WBS experiments using a tunnel scenario, with a separate knowledge-graph audit. | Imagine delivering a tunnel beneath the Solway. | ontology, WBS, knowledge graphs | An ontology, a WBS and a knowledge-graph audit answer different questions; none alone establishes tunnel feasibility. GitHub source (may require access) |
| Knowing enough to act together | What must each crew know to choose its part of the move? Compare route cues, completion reports and direct inspections to test whether local information lets each crew choose a safe action. Handlers choose a passage; the curator decides whether to reopen. | Move an oversized whale exhibit through a museum. | knowledge, coordination, project state | Finite checks ask whether each crew can choose a safe action from its local information. They do not optimise a resource schedule or demonstrate human benefit; the museum is one provisional setting. GitHub source (may require access) Public End, Ways and Means |
| Bracken Vale: useful project interventions | Which small interventions help project people see and do something useful? Practical trials explore project decisions, relationships, measures and evidence-linked drafts in a railway. Inputs and results stay inspectable; practical human benefit remains to be tested. | A small railway has renewals to plan, decisions waiting and several accounts of what matters. | project management, decisions, evidence, relationships | First-version coverage does not establish adoption or practical human benefit. GitHub source (may require access) Public End, Ways and Means (3 October 2026 copy) |
| Learning from what we keep | Does feedback improve the next review? Test feedback transfer and preservation of judgement, from a synthetic desk to fresh language-model trials. | Decide which project briefs to keep, correct or reject. | feedback, judgement, learning | A synthetic learner and six fresh model sessions on supplied briefs. Rubric ambiguity limits the apparent feedback gain; no advantage for scoped preparation, human benefit or lasting model learning is established. GitHub source (may require access) |
| Does the picture change the judgement? | Can the same facts lead us to a different judgement? Compare complete tables and aligned diagrams, inspect model readers’ decisions and revisit summary omissions. | Take over a project and decide what can proceed. | representation, judgement, handover | Matched cases with explicit rules and known answers. Four screenshot-reading model sessions reached a ceiling with both forms; no representational advantage, faster reasoning or human benefit is established. GitHub source (may require access) |
| A useful answer sold by the piece | What useful professional result can be bought separately? Test the boundary, acceptance and effort of a small dependency-checking commission. | Buy a dependency check with a clear acceptance boundary. | services, acceptance, dependencies | Executable checks and adjustable cost assumptions. No buyer demand, professional acceptance, sale or realised client benefit is claimed. GitHub source (may require access) |
| Keeping construction methods open | Can we still change the way we build it? Two essais explore crew feasibility and the point at which completed work closes a route to another construction method. | Build a bridge between two peaks while keeping another method possible. | construction, options, resources | A six-job resource scheduler and a separate finite construction-state model. Retained drawing interpolation and task affinity do not establish feasible construction transitions. GitHub source (may require access) The two bridge essais |
| Business project benchmark | Can the next model give a better answer to the same project question? Three retained essais across two declared input suites: a shared business case, then twenty distinct project settings. Comparisons stay within their suite. | Essais 1 and 2 share a two-hub repair service; Essai 3 uses twenty distinct project settings. | benchmark, consulting, models | Twenty interactive answers to one fixed business-project case. The first run was developed with assistance and repairs; scores start unreviewed. No improvement trend or client benefit is established. GitHub source (may require access) Repeatable question pack and run method |
| Hidden opportunities within reach | What better arrangement of work are we walking past? Foray 246 begins with a fictional director, six possible arrangements of work, linked ordinal maps and a reusable prompt open to better methods from future models. | Mara Venn keeps six museum retrofits moving by personally translating their handovers. | opportunities, equilibria, services, professional work, small multiples | An invented director and authored ordinal opportunity map. Assumed rewards and counterfactual rules show tradeoffs; they establish no measured equilibrium, market demand or personal recommendation. GitHub source (may require access) Method, data and limits Open foray prompt |
| Meta Project Innovation | Could we improve the project before optimising its plan? Six lenses on an island observatory retain demand, evidence, capability compilation, scarcity, dependencies and scheduling. A separate asset-inheritance essai asks what the first project makes possible for successors. | Open Skarra island observatory for one public weekend before the winter ferry stops. | project management, planning, evidence, capability, innovation | Demand and evidence feed the capability packet; scarcity, dependencies and scheduling remain separate. Asset inheritance is a separate fixed-catalogue feasibility model, not evidence of opportunity discovery or realised economic benefit. The wider enquiry remains open. GitHub source (may require access) Original proposals, pilots and source deck Asset inheritance: source, construction and limits |
| Counterfactual programme steering | What would change if we chose a different management policy? Project Causal Lab pairs a causal-graph explorer with a separate programme-policy model. An early Counterfactuals trial, with the boundary between assumptions, fitted data and causal evidence made explicit. | An archive manager must choose a six-week pilot: automate more, add cataloguers or limit unfinished batches. | causality, counterfactuals, decisions, simulation | A causal-graph explorer and a separate policy model. Supplied assumptions, fitted data and causal evidence must remain distinct. GitHub source (may require access) |
| Finding and changing abstraction layers | How can we find useful layers of abstraction, and change them when they fail? An open enquiry beginning with a historical model response: a proposed heuristic kit, failure taxonomy and layer-shift protocol. | Six railway workfronts share follow-up work; a roving crew must be dispatched using a useful reporting frame. | abstraction, complexity, models | Three bounded essais: a historical heuristic kit, an exact-arithmetic hidden-distinction example, and a synthetic pairing search separating agreement, stability and action loss. Structural fit alone does not establish decision quality or practical benefit. GitHub source (may require access) Essai 1 and historical sources Essai 2 and reproducible calculation Essai 3 and the interactive grouping search |
| Testing an open-source PDA platform | Which delivery decisions does an open-source platform actually improve? Foray 285 begins with Winter Fleet. PDA retained changes and assumption drift; ordinary reference calculations supplied the decisive capacity and cash answer. The wider enquiry remains open. | Winter Fleet: keep 48 existing promises while weighing seven new jobs, boat availability, qualified crews and cash. | project delivery, analytics, resources, evidence, open source | A recorded fictional trial, not a live PDA service or operational integration. Changes and assumption drift persisted; capacity and cash decisions came from separate reference arithmetic. No additional PDA decision value or human time saving was demonstrated. GitHub source (may require access) The foray’s End, Ways and Means Essai 1: Winter Fleet and exact evidence |
| Portfolio Wave reading map | How do sources, themes and projects connect? Explore the public source–project–topic projection through the Portfolio Wave view of the concepts graph. | Follow a reading idea into a project experiment. | knowledge graphs, sources, projects | A public source–project–topic projection. A link suggests a reading connection, not proof that the source establishes a project's claims. GitHub source (may require access) |
| Tag Concurrence Graph | Which concepts occur together in reading and app collections? Concepts-graph views for reading collections and a dated React app-catalogue tag map, with explicit source and refresh information. | Find connections in a shelf of tagged reading. | knowledge graphs, sources | Co-occurrence maps describe the indexed collection and its refresh state; an association is not a causal or semantic proof. GitHub source (may require access) |
| Can we rely on project research? | What survives when we follow a project claim back to its evidence? Foray 265 begins with a source audit and a reproducible reconstruction. Missing evidence, failed reproduction and misconduct remain distinct. | Follow a project-management paper from its reported method to an independently checkable result. | research, evidence, reproducibility, project management | Source audits and bounded reconstructions do not establish misconduct, validate every conclusion or replace independent replication. Citation reach and research reliability are separate questions. GitHub source (may require access) The foray’s End, Ways and Means Essai 1: evidence, method and limits |
| Where to draw the work | What can one crew take for granted about the next? Try six ways to divide the work between a tour and its host. Compare what the school can book before departure with what the host can deliver on the day. | A school asks for a hosted family session in Lowestoft after the exhibition train leaves. | work packages, coordination, category theory | The two-unit allowance, four-hour duty, availability and authority are assumed. The historical exhibition supplies the setting. The school request is imagined. GitHub source (may require access) Worked argument and public sources |
Library subjects and evidence boundaries
Library examples are more established or reusable, not certified. A working interface, model check, mathematical proof and demonstrated human benefit establish different things. Read the chosen example’s assumptions and limits.
- Project states & relationships — Connect tasks, states, people and resources. Explore shared project models, process diagrams and the relationships behind a portfolio. (20 entries)
- Decisions & trade-offs — Frame a decision, compare competing objectives, and inspect what buffer, delay assumptions and new information change. (14 entries)
- Delivery dynamics & feedback — Explore dependency loops, learning, rework, reviews and site occupancy through deliberately small models. (14 entries)
- Data, evidence & assurance — Match methods to the available information. Examine data maturity, project controls and what earlier prediction experiments could establish. (13 entries)
- Capabilities & futures — Explore the practices, capabilities and tools a portfolio might need, with earlier reading, framework guides and clearly labelled future scenarios. (17 entries)
- Custom GPTs — coaches, co-pilots and agents for thinking through project work.
Further shelves: Wider interest · Sitemap · Earlier site background. Wider interest has 11 pictured entries.
Reading the pictures (111 views)
Working views shows representations used inside the examples. Read each caption, depicted state and limitation. A screenshot records one view, not the model’s validity or current state. Text descriptions remain available when pictures or interaction are unavailable.
Hover or focus for a hint; open a picture for its caption, “Look for”, “Keep in mind” and “View shown”. The preview links to the full image and its original example. Read all visual descriptions in Markdown.
Experiments 8
Composing projects 10
10 enquiries and collections
- Gimmer: processes to plans 16
16 example entrances
Sixteen primary attempts retain their historical app numbers. The scheduling and comparison routes of App20 are two views of one attempt.
- Project process and task explorer 0
- WBS via PDDL 0
- Processes to plans: shed on a cliff 0
- Build-a-shed mini-generator 0
- Petri net to WBS to schedule 0
- Processes to plans: halfway up a cliff 0
- Cliff shed event structure 0
- Mountain shed WBS from a Petri net 0
- Process-first project model 0
- Petri net checks 0
- Build a shed with split materials 0
- Cliff refuge mini-generator 0
- Composition of complex systems 0
- Generate refuge schedules from process rules 1
1 variants
- Cliff refuge: Petri net to WBS 0
- Constraint-to-Plan Studio 0
- Integrated risks & tasks 1
1 example entrances
One essay and interactive lane model with several representations, not a separate app per section.
- Project Co-design 6
6 example entrances
Six separately modelled essays, with one distinct app per question.
- Bricklaying a Rotunda 7
7 example entrances
Seven maintained essay entrances. Companion sources and method pages are not additional experiments.
- Local to Global 10
10 example entrances
Nine later essays and one early-interpretation hub. The hub opens into six distinct variants; the two enquiry purposes remain separate.
- Early Tangled Triangle interpretations (six variants) 6
6 variants
- Regional Signalling Control Centre – Site Geometry & Topology (Concept Sketch) 0
- Tangled Triangle — Concept Geometry Sketch (Plan + Section) 0
- Tangled Triangle – Conceptual Plan & Section (Interactive) 0
- Regional Signalling Control Centre — Interface Topology Sketch (v0) 0
- Regional Signalling Control Centre – Concept Sketch & Architecture Options 0
- Regional Signalling Control Centre – Concept & Architecture (v0) 0
- Scope coherence 0
- Project director view 0
- The Tangled Triangle 0
- Patch validator 0
- Whose estimate becomes the plan? 0
- Who must agree after scope changes? 0
- Which local plans can work together? 0
- The blueprint mnemonic 0
- The navigation mnemonic 0
- Early Tangled Triangle interpretations (six variants) 6
- Shared waters: open systems 4
4 example entrances
Four distinct corrected attempts, including service capability; shared reading does not add to the attempt count.
- Gimmer: higher-autonomy experiments 6
6 example entrances
Six maintained essais retain numbers2–7, including the newer Open-net reference. The lab index and two earlier graphs remain background within shared reading, not additional essais.
- Functors for Projects 16
16 example entrances
Sixteen entries in the opening catalogue. This is an exploratory collection, not one bounded foray.
- Grounded theory and a finite colimit 0
- The atlas: ideas and explanations 0
- The atlas: explore a project graph 0
- Three-way project relationships 0
- Currying: changing the shape of a mapping 0
- Products, coproducts, pullbacks and pushouts 0
- Presheaves and opposite categories 0
- Functors as objects 0
- Models and natural transformations 0
- The Island Reading Room: policies in conversation 2
- Milestones under changing constraints 0
- Sheaf-style schedule playground 0
- Group actions for project thinking 0
- Galois adjoints 0
- Category theory construction toolkit 0
- Composable uncertainty wiring 0
- Building a Wall 13
13 example entrances
Thirteen entries in the app catalogue linked from the head, including six wiring-diagram essays. Counts describe entrances, not maturity.
- Keep the interfaces honest 0
- One diagram, several meanings 0
- How a course repeats 0
- The drawing that forks 0
- Good snapshots. Bad history? 0
- The same package, a different assembly 0
- Wall-building wiring diagram (W) 0
- Wall wiring diagram (SMC/Operad) 0
- Construction as an Operad Algebra 0
- Wall + Roof Contracts Algebra 0
- SysML wiring comparison 0
- Cliff shed WBS dual view 0
- Petri → SMC → WBS (Brick Wall) 0
- Where to draw the work 1
1 example entrances
One essai with an interactive handover, a worked argument and a printable production sheet.
Named entrances from each opening page or its linked catalogue. The counts do not rank their maturity or claim completeness.
Planning and judgement 12
12 enquiries and collections
- Programme Decision Sequences 12
12 example entrances
Twelve catalogue entrances retain their current native order and historical-report label. The two-tab climate lab is one attempt.
- When is evidence worth waiting for? 0
- Enough to hand over? 0
- What made the forecast improve? 0
- What was known at the time? 0
- How old is the picture you act on? 0
- Sequence, belief & policy lab 0
- Climate policy simulator 0
- Project decision framing 0
- Two climate decision paths 0
- IT project decision tutorial 0
- Weekly IT project game 0
- Climate SDAM snapshot 0
- Project Spines 3
3 example entrances
Three distinct essais: exploring work order, positive spine constructions, and choosing concurrent work. The first retains eight views; views and shared reading tiles are not additional attempts.
- Solway Tunnel Ontology 15
15 example entrances
Fifteen current native catalogue entries. The earlier duplicate tunnel visualizer remains an unchanged forwarder to the maintained ontology explorer, not another attempt.
- The handover game 0
- The work that must exist 0
- When the work changes 0
- What does this measurement justify? 0
- Digital Construction ontology — early essai 0
- What does this project link say? 0
- Solway ontology explorer 1
- global-WBS-by-sheaf 0
- sheaf-wbs-prototype 0
- two-possible-means 0
- solway-firth-tunnel-fibration-demo 0
- solway-sheaf-wbs-prototype 0
- sheaves-for-tunnel-concept 0
- ontologized-allen-schedule 0
- kglab-ontology-audit 0
- Knowing enough to act together 2
2 example entrances
Two separate essais: local information for moving the whale, then one workable choice. Both models and their original saved/shareable settings remain distinct.
- Learning from what we keep 2
2 example entrances
Two bounded interactive essais. The wider enquiry remains open.
Scenario, purpose and shared ideas
- Purpose 0
- Keeping construction methods open 2
2 example entrances
Two first essais: resource feasibility and construction-method switching. Geometry and task-field explorations remain available in the second essai.
- Business project benchmark 3
3 example entrances
Three retained essais. Essais 1 and 2 use one shared project; Essai 3 tests twenty distinct project scenarios with separately attributed scores. Different suites are not directly comparable.
- Essai 1 · Shared project baseline 20
20 variants
- 01 · Plan and forecast 0
- 02 · Exception radar 0
- 03 · Delay register 0
- 04 · Shared control room 0
- 05 · Update attribution 0
- 06 · Lessons retrieval 0
- 07 · Daily leadership brief 0
- 08 · Meeting cadence 0
- 09 · Decision rhythm 0
- 10 · Skills and capacity 0
- 11 · Action and evidence 0
- 12 · Conflicting reports 0
- 13 · Test portfolio 0
- 14 · Evidence and constraints 0
- 15 · Procurement choices 0
- 16 · Stakeholder story 0
- 17 · Hostile-input drill 0
- 18 · Alternative plans 0
- 19 · Tool landscape 0
- 20 · Controlled integration 0
- Essai 2 · Twenty separate browser answers 20
20 variants
- 01 · Plan and forecast 0
- 02 · Exception radar 0
- 03 · Delay register 0
- 04 · Shared control room 0
- 05 · Update attribution 0
- 06 · Lessons retrieval 0
- 07 · Daily leadership brief 0
- 08 · Meeting cadence 0
- 09 · Decision rhythm 0
- 10 · Skills and capacity 0
- 11 · Action and evidence 0
- 12 · Conflicting reports 0
- 13 · Test portfolio 0
- 14 · Evidence and constraints 0
- 15 · Procurement choices 0
- 16 · Stakeholder story 0
- 17 · Hostile-input drill 0
- 18 · Alternative plans 0
- 19 · Tool landscape 0
- 20 · Controlled integration 0
- Essai 3 · Twenty distinct project scenarios 20
20 variants
- BPB2-01 · Youth centre refurbishment — define the commission 0
- BPB2-02 · Freight depot electrification — make the investment case 0
- BPB2-03 · Museum refurbishment — produce a credible opening plan 0
- BPB2-04 · Rural broadband rollout — forecast the final cost 0
- BPB2-05 · Offshore inspection campaign — choose responses and contingency 0
- BPB2-06 · School meals ordering system — select a supplier 0
- BPB2-07 · Aerospace prototype programme — allocate scarce specialists 0
- BPB2-08 · Office fit-out — assess a late change 0
- BPB2-09 · Charity CRM replacement — choose the first release 0
- BPB2-10 · Water utility asset migration — establish a trustworthy status 0
- BPB2-11 · University laboratory — brief the board honestly 0
- BPB2-12 · Outpatient service redesign — secure a workable agreement 0
- BPB2-13 · Tram extension — resolve delivery interfaces 0
- BPB2-14 · Retail payments migration — recommend go or no-go 0
- BPB2-15 · Food production line — organise acceptance and handover 0
- BPB2-16 · Housing energy retrofit — test realised benefits 0
- BPB2-17 · Wholesale ERP implementation — recover delivery 0
- BPB2-18 · Visitor attraction development — continue, pause or stop 0
- BPB2-19 · Solar farm construction — use previous experience intelligently 0
- BPB2-20 · Community festival — turn discussion into controlled action 0
- Essai 1 · Shared project baseline 20
- Hidden opportunities within reach 1
1 example entrances
Foray 246 opens with a fictional museum delivery director, six nearby arrangements, linked ordinal maps and tests of the assumptions. No economic equilibrium or commercial demand is established.
- Meta Project Innovation 2
2 example entrances
Frontier Lab retains its six internal lenses. A separate asset-inheritance essai compares successor feasibility under equal later funding; it does not combine the lenses into an optimiser.
- Finding and changing abstraction layers 3
3 example entrances
Three essais: a historical heuristic kit, an exact-arithmetic hidden-distinction example, and a synthetic search for replacement groupings. Practical benefit remains open to empirical trial.
- Testing an open-source PDA platform 1
1 example entrances
The first fictional case is executed. Persistent records and analytical decision value are assessed separately; broader usefulness and human time savings remain unproved.
- Can we rely on project research? 1
1 example entrances
A first source audit and reproducible reconstruction. The wider reliability enquiry remains open; this is not a misconduct finding or a completed replication programme.
Named entrances from each opening page or its linked catalogue. The counts do not rank their maturity or claim completeness.
Graphs and representations 3
3 enquiries and collections
- Does the picture change the judgement? 3
3 example entrances
Two interactive essais and a worked reading of what a handover summary must preserve. The wider enquiry remains open.
Scenario, purpose and shared ideas
- Purpose 0
- Portfolio Wave reading map 1
1 example entrances
One public source–project–topic map, with separate Scenario and Purpose reading views.
- Tag Concurrence Graph 3
3 example entrances
Three existing reading/catalogue map views, including the explicitly frozen catalogue snapshot. Shared reading is not new research.
Named entrances from each opening page or its linked catalogue. The counts do not rank their maturity or claim completeness.
Rethinking project work 3
3 enquiries and collections
- Bracken Vale: useful project interventions 1
1 example entrances
One dated essai contains32 constructions and its narrative account. These33 child reading routes are not33 independent essais.
- Essai 01 — Small interventions, useful questions 33
33 variants
- Small interventions, useful questions — the essai 0
- Which account applies? 0
- Whose outcome? 0
- A connection has a kind 0
- The constraint moves 0
- A trial worth having 0
- A signal worth seeing 0
- Small enough to agree 0
- Keep the recipe 0
- What applies here? 0
- A route that fits 0
- A meeting with a decision 0
- Checked in what sense? 0
- Useful elsewhere? 0
- Learn from the case 0
- Ready on the first pass? 0
- The missing link 0
- A gate with reasons 0
- What is in the tables? 0
- Make retreat possible 0
- What did the task list miss? 0
- A draft is not a gate 0
- Try one office job 0
- Keep the disagreement 0
- Remember before deciding 0
- Find the story in the pattern 0
- The work of getting better 0
- Practise on the artefact 0
- What does that number mean? 0
- Know now, act later? 0
- The shape of waiting 0
- Spend attention carefully 0
- The shared dependency 0
- Essai 01 — Small interventions, useful questions 33
- A useful answer sold by the piece 1
1 example entrances
First bounded interactive essai. The wider enquiry remains open.
- Counterfactual programme steering 1
1 example entrances
One essay and app containing causal-path and policy-simulation modes. The two modes are not one fitted model.
Named entrances from each opening page or its linked catalogue. The counts do not rank their maturity or claim completeness.
Other ways to browse
All experiments 0
Scenarios 24
24 scenarios
- Gimmer refuge 2
2 enquiries in this setting
- The Neidpath wall 3
3 enquiries in this setting
- The farm track 1
1 enquiries in this setting
- A wildlife crossing 6
6 enquiries in this setting
- A brick rotunda 2
2 enquiries in this setting
- The Tangled Triangle 2
2 enquiries in this setting
- Shared waters 4
4 enquiries in this setting
- A wall and its roof 3
3 enquiries in this setting
- A tunnel beneath the Solway 1
1 enquiries in this setting
- Moving the museum whale 1
1 enquiries in this setting
- Bracken Vale railway 1
1 enquiries in this setting
- The mountain-festival shuttle 1
1 enquiries in this setting
- The Island Reading Room 1
1 enquiries in this setting
- A review desk 1
1 enquiries in this setting
- A project handover 1
1 enquiries in this setting
- A small commission 1
1 enquiries in this setting
- A bridge between two peaks 2
2 enquiries in this setting
- A repair-and-reuse service 1
1 enquiries in this setting
- The museum retrofit director 1
1 enquiries in this setting
- Skarra Observatory 1
1 enquiries in this setting
- Winter Fleet 1
1 enquiries in this setting
- The archive digitisation backlog 1
1 enquiries in this setting
- Six railway workfronts 1
1 enquiries in this setting
- The second Saturday at the Parcels Office 1
1 enquiries in this setting
One familiar situation can support several different enquiries. Their example lists sit in the Experiments branch.
Working views 111
111 working views
- Is a way of moving the same as a path? 0
- Keep three kinds of thing distinct 0
- Can all five local rules agree? 0
- Can we move the whale? 0
- Which tower gets the next lift? 0
- See a complete crossing choice 0
- See the connections between tasks and risks 0
- Do three pairwise links make a joint decision? 0
- How widely do outcomes spread under one policy? 0
- Separate fit, exclusion and uncertainty 0
- Possible in every case, but can the handler choose? 0
- Give a change of position a reason 0
- Can the same handover hide different next moves? 0
- Is adapting worth the survey and the wait? 0
- When a review changes the next move 0
- An early picture of decisions in sequence 0
- Trace a risk judgement into a choice 0
- Which assumed arrow makes adjustment necessary? 0
- Keep competing explanations visible 0
- Where can this state graph get stuck? 0
- The possible journeys of a project idea 0
- A severe risk in a moderate band 0
- Four tasks, four suggested responses 0
- Influence and interest are different axes 0
- When does an answer become the next question? 0
- What must travel back across an interface? 0
- Join two modules at one handover 0
- Compose two mobilisation processes 0
- Where does the scaffolding go next? 0
- Follow the particular wire 0
- One load connection, explicit conditions 0
- Can we regroup without changing the behaviour? 0
- An early picture of composing systems 0
- Separate doing from becoming true 0
- Read just the task chain 0
- Inspect an early task-to-token translation 0
- When can the next task start? 0
- Which work is enabled now? 0
- What changes when this task is done? 0
- One result can have several histories 0
- Can the same brick count permit different next moves? 0
- Different arrows carry different obligations 0
- Keep tasks inside their wider context 0
- Let an outside process into the plan 0
- Make competition for the lane visible 0
- Put the project inside its context 0
- Threats cut across intended work 0
- Look at one project through fourteen views 0
- Find the feedback group 0
- Collapse a feedback loop into one group 0
- See what abstraction forgets 0
- Which distinctions do your coding choices remove? 0
- Reconcile four directors’ views 0
- Where do the local resource views disagree? 0
- What changed to make these plans agree? 0
- Who must agree after scope changes? 0
- Follow a change across shared interfaces 0
- What must a translation preserve? 0
- Compare two interpretations of a design 0
- Connect strategy to delivery and operations 0
- A smaller neighbourhood of the programme 0
- The full programme drawing 0
- A programme seen from operations 0
- Separate work, outputs and resources 0
- An ontology separates kinds of project information 0
- Inspect the kinds of thing in the tunnel 0
- Keep local models distinct 0
- Compose a view from local accounts 0
- Which chain crosses every work layer? 0
- A calendar bucket can contain a hidden dependency 0
- Which extra rules did the stages invent? 0
- Which schedule does this token history support? 0
- Dependencies and dates in two views 0
- Put decision times beside the work 0
- What does one more buffer day buy? 0
- Locate where the material waits 0
- Compare the schedules behind a trade-off 0
- Moving along or beyond a frontier 0
- How two uncertainties move together 0
- Watch work, learning and debt move together 0
- Keep filing, interpretation and source use distinct 0
- Which concepts occur together in the reading? 0
- Read the connections in a tagged library 0
- Test a theme against its supporting text 0
- Group records by their shared control tags 0
- What does task proximity actually mean? 0
- Turn project records into a question worth testing 0
- Different questions from the same document corpus 0
- Project records coloured by rating 0
- Neighbourhoods in projected project records 0
- Comparing four candidate classifiers 0
- Adding a graph view to project records 0
- One supplier, several investment records 0
- Activities beneath delayed projects 0
- Work classified as controls and oversight 0
- Compare a contract’s links with its places 0
- Connecting project questions to models and data 0
- Trace aspirations into proposed scope 0
- Outputs and hoped-for benefits 0
- Project gaps beside a benefits rehearsal 0
- Choose the practices a portfolio needs 0
- From a business need to a portfolio practice 0
- Find the question behind a capability 0
- Trace a learning route through project controls 0
- Inspect why a governance rule passes 0
- Keep funding and milestone claims inspectable 0
- Inspect a capability profile 0
- Empty regions in assumed capability scores 0
- A slice of the project-tool timeline 0
- Placing GPT ideas across consulting work 0
- Choosing a route from governance need to tools 0
The representations used inside the examples.
Compare 2
2 comparison cases
- Gimån footbridge 27
27 experiment findings
- Local to Global 0
- Changing project states 0
- Project Co-design 0
- Processes to plans 0
- Programme Decision Sequences 0
- Composing open systems 0
- Semantic project planning 0
- Composing work packages 0
- Integrated risks & tasks 0
- Higher-autonomy experiments 0
- Project Spines 0
- Functors for Projects 0
- Knowing enough to act together 0
- Meta Project Innovation 0
- Counterfactual programme steering 0
- Useful project interventions 0
- Learning from what we keep 0
- Does the picture change the judgement? 0
- A useful answer sold by the piece 0
- Finding and changing abstraction layers 0
- Project models in use 0
- Keeping construction methods open 0
- Business project benchmark 0
- Hidden opportunities within reach 0
- Can we rely on project research? 0
- Testing an open-source PDA platform 0
- Where to draw the work 0
- Bond Street readiness decision 0
Library 9
9 collections and entrances
Project states & relationships 20
- How should the work fit into a shared picture? 0
- Move a project through a portfolio 0
- Contract Portfolio Board 0
- How do two mobilisation processes fit together? 0
- From shed states to a candidate task structure 0
- Social Debt 0
- See a project from different seats 0
- Who needs a different conversation? 0
- How does railway scope connect to people and objectives? 0
- Read a stakeholder concept schema 0
- Following questions through a US IT portfolio 0
- What makes the next step possible? 0
- Trace outputs towards benefits 0
- Follow work into products 0
- Olaf’s afternoon deliveries 0
- Graphs & connections 0
- Data models for project portfolios 0
- Nodes and edges 0
- Explore project states and possible traps 0
- Inspect what a graph change preserves 0
Decisions & trade-offs 14
- Reframe a two-sided question 0
- Find the kind of decision you are making 0
- Compare options with weighted criteria 0
- Find a better trade-off together 0
- What do your decision weights imply? 0
- Compare a backlog with its stated priorities 0
- What does another day of buffer buy? 0
- Decide now—or find out more first? 0
- Build and interpret a risk matrix 0
- When do task delays happen together? 0
- Sort tasks by urgency and importance 0
- Follow a decision through a project graph 0
- Explore a project agreement 0
- Rehearse a regulatory negotiation 0
Delivery dynamics & feedback 14
- Find the delay that moves the finish 0
- See what a plan rewrite changes 0
- A project review changes the next move 0
- Explore the assumptions behind a delivery date 0
- Trace decisions beside overlapping work 0
- Time Exchange 0
- Find the feedback groups. 0
- How changes spread between project interfaces 0
- A software team learns and reworks 0
- Waste-route capacity 0
- A day on the pool-and-gym site 0
- See when feedback settles or grows 0
- Trace dependencies across phases and time 0
- What makes concurrent change costly? 0
Data, evidence & assurance 13
- Which method fits the question and the available data? 0
- Discuss data maturity in context 0
- Check the shape and meaning of project data 0
- What could an activity-delay forecast know in time? 0
- Inspect a governance trail 0
- Scenario and control lattice 0
- Find your way into project controls 0
- Project graph views 0
- Turn project records into a question worth testing 0
- Applying appropriate machine-learning approach. 0
- Read a crossing project through its notices 0
- Reading claims from project text 0
- Read project health and benefit assumptions 0
Capabilities & futures 17
- Which working practices does this portfolio need? 0
- Separate capability, maturity and performance 0
- Project management: Some jobs to be done 0
- Review portfolio-office capabilities 0
- Build a more useful programme conversation 0
- Match a task to a capability 0
- Idea notebook 0
- Adopt existing portfolio framework 0
- Projects by agents: closing a foray 0
- Gap Map 0
- Explore gaps in a capability map 0
- Follow the changing project-tool landscape 0
- Imagine different project-services markets 0
- Books 0
- Deep Research 0
- Compare overlapping scenario pressures 0
- Shape a useful project service 0
- Custom GPTs 0
- Wider interest 11
- Sitemap 0
- Earlier site background 0
About Lawrence and this collection 0
Visitors’ book — for visiting agents 0
What’s new · Weekly significant updates, also available via RSS.