These posts and categories collectively provide an overview and marketing rationale for a framework designed to combat the issues of AI hype and “workslop” (generic, low-quality AI output) by establishing genuine organizational intelligence. The core of this solution is the Hermeneutic Workflow Methodology (HWM), an interpretive process emphasizing human primacy, context, and philosophical reflection, and the Context Intelligence Portal (CIP), a structured knowledge system where an organization’s reasoning and judgment are codified. The documents argue that traditional knowledge management systems fail, and that executives are currently overwhelmed by AI promises, validating the need for a framework that requires a time-intensive “semantic apprenticeship” (around 200 hours) by leaders to transform tacit knowledge into reusable infrastructure, thereby turning meaning into a scalable, competitive asset.
This site’s my map in progress, part field notes, part trail markers.
I’m trying to turn human judgment into something a system can remember.
Around here I call that the Hermeneutic Workflow Methodology (HWM) and the Context Intelligence Portal (CIP).
It feels less like a project plan, more like a long walk.
I write for brand owners, stewards, and people who live with complex meaning every day.
If you care about context, tone, and what a message’s trying to accomplish, you’re home.
Why this blog exists
First, this white paper laid out a confident model. But it was a first draft of an idea written without resolving various loose ends. It left much to be worked out. And now…
This blog slows down and works it out in public.
I test ideas, mark dead ends, and show where the thinking needs more shape.
The goal’s useful clarity, not slogans.
Three simple aims:
-
Name the work of capturing organizational judgment.
-
Show how it can live in a system without losing the human point.
-
Leave a map others can reuse and improve.
The short version
-
HWM’s the working method, a repeatable way to surface tacit reasoning.
-
CIP’s the place that reasoning lives, a queryable home for your “why.”
-
The point’s practical wisdom — phronēsis, if you like the Greek word.
-
The outcome’s fewer re-explanations, fewer revisions, and messages that land.
The long version
If you want the background, the first draft of the framework lives here:
Building Context Intelligence for the Next Decade
It’s a public white paper that laid out the early version of these ideas.
It’s confident, a little overbuilt in places, and still the best snapshot of where this all began.
This blog’s here to keep testing and refining what that paper started — turning the theory into something you can actually use.
Who this is for
-
Brand owners, founders, and domain stewards who carry the reasoning behind a product or organization.
-
People who think about judgment, tone, and coherence at scale.
-
Leaders who feel the pain of context loss when meaning gets spread across teams, tools, or time.
-
Builders, researchers, and systems thinkers who want to see how practical wisdom can live inside digital frameworks.
If you’re the one who always ends up explaining “why” things are done a certain way, this work’s for you.
If you’d rather delegate that explaining, it probably isn’t.
What problem we’re solving
Every team’s got a pile of documents.
Very few teams can show the reasoning under those documents.
That’s why work gets redone. That’s why tone drifts.
That’s why “brand voice” feels fragile.
We fix that by making the reasoning visible.
We give it a home you can query.
We keep the human in charge of judgment.
What HWM is in plain language
HWM’s a working rhythm:
-
Gather live examples that show real intent.
-
Ask simple questions until the “why” is clear.
-
Write the rationale in small, reusable chunks.
-
Check those chunks against new cases.
-
Keep only what holds up.
-
Version it, date it, own it.
It’s steady, patient work.
Think of it like training a new hire who doesn’t forget.
What the CIP is
A structured space where your judgment lives.
Short entries, clear links, tight definitions, honest examples.
It answers questions like:
-
What did we mean by that phrase?
-
Who’s the audience, and what do they value?
-
What outcome defines success for this message?
-
How do we decide when to bend a rule?
People can query it.
Language models can read it.
The steward decides what’s true enough to ship.
Why practical wisdom matters
Rules help. Checklists help.
Real work still needs judgment in the moment.
Phronēsis is that kind of judgment.
It lives between principles and the case in front of you.
HWM’s how we surface it.
CIP’s how we keep it.
What this isn’t
-
It’s not a content mill.
-
It’s not a “replace the team” pitch.
-
It’s not a search engine for facts.
-
It’s not a brand book with nicer colors.
It’s a way to preserve and share how your team decides.
So people can act with confidence.
Why not just use retrieval tools
Retrieval finds files.
Reasoning explains choices.
We need both.
HWM and CIP make retrieval worth something, because the “why” is present.
Where the time goes
Plan on 150 to 200 hours for the first serious pass.
It sounds heavy.
It’s less than the time you already spend repeating yourself.
-
Week 1–2, collect examples and write the first stubs.
-
Week 3–6, refine definitions, edge cases, and tone rules.
-
Week 7–8, wire the links and test with a small circle.
-
Ongoing, add, trim, version, and retire stale logic.
Small team. Tight scope. Clear owner. That’s the pattern.
What success looks like
-
Fewer rounds of revision.
-
Faster onboarding without loss of tone.
-
Decisions that feel consistent across teams and months.
-
Vendors who deliver on the first try.
-
Writing that sounds like you, across languages.
You’ll feel it first in your calendar.
Then you’ll see it in the work.
What I believe about ownership
One person needs to own meaning.
A small circle can help.
The steward carries the final call and the responsibility.
That’s how coherence appears.
How to use this site
-
Start with the “What is HWM and CIP” post.
-
Skim the FAQ for a feel of the edges.
-
Read the field notes, short and honest.
-
Check the directory posts when you want sources and tools.
-
Use the glossary if a term feels fuzzy.
You don’t need to read in order.
Follow your questions.
Tooling, lightly
Use what you’ve got.
A careful doc system’s enough for a pilot.
Many teams like a secure notes database, a clean Wiki, or a reasoning notebook.
Later, add search, access rules, and audit trails.
Keep the structure simple. Keep the language exact.
How to start a pilot
-
Choose one product line or one campaign.
-
Pick ten real pieces of content that matter.
-
Write the intent and audience for each piece.
-
Pull out recurring moves and traps.
-
Draft definitions for the top twenty terms of art.
-
Ask two outsiders to try it.
-
Ship a small project using only the written guidance.
-
Fix what breaks.
-
Version the set and call it a win.
Then repeat for the next slice.
Common questions
Can a model build the CIP on its own?
No. It can draft and compare. The steward decides.
Can we delegate the work to a junior analyst?
They can help gather and format. The owner still has to say what’s true.
What if our voice changes?
Good. Version the portal. Date the change. Explain why.
Will this slow us down?
At first, a little. Over time, the work gets faster and cleaner.
Does this replace a brand book?
No. It complements it. The brand book shows the surface. The portal shows the logic.
What about privacy?
Keep the source set small and secure. Limit access. Log changes.
Use private tooling if you can. Ask legal early.
A simple structure for entries
-
Name, short and exact.
-
Purpose, one or two lines.
-
Audience, who and why they care.
-
Reasoning, a few bullets that carry the why.
-
Examples, real lines that worked.
-
Red lines, what we won’t say.
-
Cross links, where to look next.
-
Version, date, and owner.
Keep entries small. Edit without drama.
Retire what no longer helps.
What’ll show up here
-
Walkthroughs of small pilots.
-
Patterns that repeat across projects.
-
How to write better portal entries.
-
How to test decisions against real cases.
-
Notes on tone, audience, and persuasive intent.
-
Reflections on phronēsis in everyday work.
-
Pointers to useful research and tools.
I keep theory tight and practical.
Ideas are only as good as the next deliverable.
How to read the white paper after this
Use the paper for the big picture.
Use this site for “show me how that works.”
Together they’re a map.
This blog keeps the map honest.
If you’re a builder of tools
There’s room to make this easier.
Models handle structure well.
They do better when we give them real intent, audience, and examples.
I hope these notes spark better ways to capture and serve reasoning.
If you build tools in that space, reach out.
If you only read one thing
Write down your “why” for one piece of live content today.
Audience, desired outcome, reasons for word choice.
Then ask someone else to ship a revision using that short entry.
You’ll feel what the CIP’s trying to do.
Reach out
If you’ve got a case, a stuck point, or a small win, I’d like to hear it.
If you disagree, even better.
This work grows through careful pushback.
Thanks for stopping by.
Let’s make meaning travel.