Decision Architecture
Field notes, concepts, and frameworks for how decisions happen.
Research at Fragment Practice is where observations from real work are turned into concepts, language, and reusable structures.
If Services is where operating models are shaped in practice, Research is where those recurring patterns are named, clarified, and developed into the building blocks of Decision Architecture.
This includes field notes, conceptual essays, practical frameworks, maps, patterns, and applied studies that connect human judgment, organizational structure, and AI-enabled work.
Looking for practical engagement formats? See Services (JP). Looking for the broader studio context? See About.
What you’ll find here
Who this is for
- Practitioners trying to make AI-enabled work more governable.
- Researchers and writers interested in decisions as a field of study.
- Leads, operators, and advisors working at the boundary of AI and human judgment.
Practice → research → field
Fragment Practice runs on a simple loop: observe recurring decision problems in real work, abstract them into concepts and frameworks, then return them to practice in a reusable form.
- Decisions disappear across meetings, chat, docs, and tools.
- AI is useful, but accountability becomes unclear.
- Review points and exception paths remain implicit.
- Teams move faster than their structures can explain.
- Patterns are named and turned into concepts.
- Concepts are tested through frameworks and field notes.
- Frameworks become reusable language for future work.
- The field slowly becomes legible to others.
Main lines of research
The research currently develops across four connected lines.
How decisions actually move through meetings, notes, logs, approvals, handovers, and AI-supported workflows.
- Decision boundaries between drafting, reviewing, and deciding
- Decision trails that survive time, scale, and handovers
How review, escalation, documentation, and policy interact with AI-enabled decisions in practice.
- Governance that teams can actually sustain
- Accountability structures that remain visible under automation
The internal language of the field: maps, principles, canvases, and patterns that make Decision Architecture communicable and practical.
- Decision boundaries, logging, escalation, and drift
- Frameworks for structuring human–AI operating models
Essays, ZINEs, and applied notes that connect everyday life, work, institutions, and AI through the structure of decisions.
- Short-form writing as conceptual iteration
- Public language for an emerging field
Core layers
These are not “theories” in the abstract. They are working layers for deciding what to structure, where to draw boundaries, and how to keep systems legible.
Decision boundaries
A central research layer focused on where authority shifts between actors — humans, teams, organizations, and AI systems.
Decision logs
Research into how decisions can remain readable, reviewable, and auditable after the moment of action.
Escalation and review
How difficult cases move through systems, and how review loops transform individual decisions into organizational learning.
Boundary drift
Research into the gradual movement from AI assistance to AI default authority — often without explicit redesign of responsibility.
Method
Research begins small. The goal is not scale first, but legibility first.
Observe
Start from a real decision problem in practice: repeated ambiguity, missing trails, unclear ownership, or unsafe acceleration.
Abstract
Translate recurring problems into concepts, distinctions, or design patterns that can travel beyond the original case.
Return
Bring those concepts back into practice through advisory work, writing, and public language that others can reuse.
Outputs
Research is published in forms that remain readable and reusable.
Frameworks / field notes
- Concepts, maps, principles, canvases, and pattern libraries
- Case-derived notes rewritten into reusable language
ZINE / essays / talks
- Short-form writing that connects life, work, and decision structures
- Public-facing language for an emerging field
Where to go next
Research is the conceptual backbone. ZINE is often the most accessible entry point. Services is where these ideas are translated into operating models.