Killough Works
The Methodology
We help people and organizations make sense of complexity. This is how we think.
The problem
Most difficult situations do not arrive as clean problems. They arrive as messages, meetings, conflicts, requests, transcripts, and half-formed stories — emotionally charged and easy to misread.
People and organizations rarely fail because they lack tools. They fail because complexity arrives faster than clarity. Narratives replace original issues. Urgency replaces preparation. Someone must decide before anyone has made sense of what is actually in front of them.
Killough Works exists to close that gap — without pretending that any system, human or machine, can claim final authority over truth.
The philosophy
Understanding comes before action. Preparation comes before reaction. Structure comes before verdict.
The work assumes that messy input can be organized for human review — that clarity means legibility for decision, not comfort theater or false certainty.
This is structured assistance, not truth verification. The goal is not to tell people what happened, what to feel, or what to believe. The goal is to help them see what matters before they act.
- Space between feeling and response. Slowing down is more valuable than speeding up reaction — especially in emotionally charged situations.
- Narratives replace original issues. People often argue about stories, not the original problem. Naming that replacement is part of the work.
- Structure assistance is not truth verification. Systems organize signals. They do not adjudicate reality or determine who is correct.
- Disputes may remain open. Competing interpretations with supporting evidence can sit side by side. Forced closure is a failure mode.
- Memory must be externalized. Continuity requires files, archives, and recall systems — not hope that someone will remember.
- Complexity absorbed by the system. Users should not navigate dispute matrices or clinical machinery. Calm interfaces hide difficult work.
- Local ownership where possible. Offline-capable archives and optional cloud enhancement — not dependency loops for basic function.
- Conversation must become owned action. In community contexts, talk without recap discipline and assigned next steps is treated as waste.
The methodology
Seven stages repeat across years of work — conversation tools, community operations, research, ministry technology, and personal systems. The stages are constitutional. The product names are implementations.
Internally, this pipeline is often called the Signal Method — a working name tied to early implementations. Publicly, we describe it by its stages until a permanent name is earned through use.
1Capture
Messy human input arrives — a message, transcript, meeting, conflict, client request, or research question. Capture accepts the mess. It does not wait for a clean version.
Not this: Not curated input. Not pre-judged facts.
See this stage in practice
2Localize
Store what was captured where the person or organization can own it. Archives should survive without always-on connectivity.
Not this: Not cloud-mandatory SaaS. Not telemetry as the system of record.
See this stage in practice
3Extract
Pull patterns from the archive: tone, claims, misunderstandings, key signals, needs. AI may assist. It does not verdict.
Not this: Not diagnosis. Not "what really happened."
See this stage in practice
4Structure
Organize into summaries, disputes, risks, next steps, and open questions — a situation someone can review, not a single imposed narrative.
Not this: Not forced resolution. Not one correct story.
See this stage in practice
5Hold
Preserve open disputes. Note confidence levels. Keep competing interpretations visible. An unresolved dispute with clear evidence is a valid end state — not a bug.
Not this: Not premature closure. Not "the AI determined the answer."
See this stage in practice
6Brief
Surface what needs human attention now: a daily overview, a situation board, a recap before a meeting closes. Briefing is curation for attention, not engagement maximization.
Not this: Not an overwhelming dump. Not an infinite feed.
See this stage in practice
7Decide
Human preparation and action. Review before send. Recap before close. Service before scatter. Software stops here.
Not this: Not auto-send. Not auto-post. Not dependency on the system for judgment.
See this stage in practice
Why Hold comes before Decide
Most systems rush to resolution. They treat an open question as incomplete work.
This methodology treats Hold as constitutional. Maps competing interpretations to evidence. Does not determine who is correct.
Decide is the last stage because human judgment — not software output — is the only legitimate place for action.
Real examples
These projects do not define the methodology. They demonstrate it — each one applying specific stages to a different kind of messy input.
Feltabout
Feltabout applies this methodology to conversation preparation — creating space between feeling and response before someone acts.
An implementation focused on reflect-before-react. Not therapy. Not a companion. Not truth verification.
Signal Map
This project demonstrates the Extract and Structure stages in a transcript workflow — messy conversation to grounded summary, risks, and next steps.
Structured assistance, not truth. Confidence notes, not verification.
Signal CLI
Signal CLI applies evidence archiving, dispute matrices, and situation boards — disputes remain open while attention is prioritized.
Maps competing interpretations to evidence. Does not determine who is correct.
Council Hub and Arbor Vitae
This organizational work demonstrates recap discipline — Tuesday conversation converted to written decisions and owned action.
Conversation must become owned action, or the conversation was wasted.
Research practice
Forensic research applies the methodology to claims and evidence — testing assertions against text, history, and documented behavior.
Public work describes patterns and method. Private dispute detail stays internal.
Truth For These Times
TFTT is a satellite ministry platform — a separate brand. Killough Works documents how forensic study tools were built, not what visitors should believe.
Parent institution, not parent brand. Cross-link intentionally; mission stays with the ministry.
The role of AI
AI may help extract patterns from messy input. It processes; it does not decide.
In this work, AI is bounded, optional, and non-authoritative. It does not determine what is true, what you should feel, or what you must do.
They are not paying for access to tools alone. They are paying for someone else handling the messy middle — and for systems that keep human judgment in the final step.
Why humans still decide
Every party in a conflict is still human — even when someone is wrong or harmful. The work humanizes; it does not villainize or pathologize.
People need clarity more than comfort theater. Precise language and actionable next steps matter more than emotional performance.
Reflect before you react. The institution exists to create that space — then get out of the way.
How evidence is handled
Claims should trace to source material. Confidence levels should be stated when conclusions are strong. Speculation should be labeled speculation.
In research, claims are tested against text, history, and documented behavior — not accepted because an institution says so.
In products, evidence links to messages, transcripts, and documents — without the software pretending to verify which side is right.
What we refuse
Knowing what you reject defines a practice as much as what you build. These refusals apply regardless of revenue or trend pressure.
Software
- Truth-verification machines. Software that pretends to know what happened or who is correct.
- Therapy or companion dependency. Diagnosis, pathologizing, or emotional dependency framing.
- Auto-send without human approval. Public action without review.
- Gamified engagement loops. Feeds, streaks, and compulsive interaction patterns.
Business
- AI magic as the product. Selling access to tools instead of judgment, structure, and finished clarity.
- Conversion-bro positioning. Desperate, money-first, or impressiveness-first marketing.
- Public self-service checkout as identity. A storefront posture where comprehension should lead.
- Agency theater. Impressive vision without shipped, honest work.
- Scope before vertical slice. Expanding before one honest slice ships.
Experience
- Visual noise and urgency. Alarm states and reactive UI that replace calm review.
- Therapy worksheet UX. Exposing clinical machinery users should not have to operate.
- Over-validation. Emotional performance without structure.
Where this appears across Killough Works
The methodology is the thread. Products are implementations. Research applies the same discipline to claims and evidence. Publishing and field notes document how the stages appear in real builds.
Feltabout, Signal tools, community operations, ministry technology, and forensic research look like separate domains. They are surfaces of one practice: making messy human situations legible for human decision.
As the site grows, each section — products, research, writing, studio work — should point back here. Not because this page is the whole institution, but because it is the center that keeps everything else coherent.
- ProductsComing — implementations of this methodology
- ResearchComing — public index of analytical work
- JournalComing — field notes from the studio
This methodology is a living body of work. As new projects, research, and experience accumulate, the language and examples may evolve while the underlying principles remain.
Revision history
- — Initial publication via publishing engine migration.