The archive grows. Its value doesn't.
Pages compete, decay or disappear. The best answer becomes hard to find.
I'm Joel Falconer. I diagnose the architecture behind large content and knowledge operations — what should exist, how people and machines find it, where it leads and whether the team can sustain it.
If writers, SEO or AI have produced activity without authority, demand or revenue, production is not the constraint. I find the structural one and rank the decisions that resolve it.
AI made production abundant. It did not decide what deserves to exist, which evidence supports it, how it will be retrieved or when it should be removed.
Four symptoms of the same structural failure.
Pages compete, decay or disappear. The best answer becomes hard to find.
Production accelerated without stronger evidence, distinction or a reason to cite you.
Search captures demand without creating product value or an owned relationship.
Decisions live in people's heads. Standards drift and ownership blurs.
A bounded engagement resolves what changes, in what order and who owns it.
Keep, consolidate, rebuild, reroute, prove, defer or remove — ranked by leverage and dependency.
The evidence and pathways that let people and AI systems find and trust what matters.
Ownership, workflow, AI boundaries, review gates and measurement — written for the team to run.
Best fit: a live archive or knowledge operation, access to evidence and an owner who can act.
Test the fitAcross web and email: 2.5 billion impressions and periods above 1.6 million weekly pageviews. The job was deciding what to preserve, connect, consolidate, redirect — and stop carrying.
I turned a deferred taxonomy problem into rules, controlled batches and editorial QA — the same governance problem now appearing in semantic retrieval.
Before ChatGPT, editorial intake and curation connected forms, automation and machine classification. Repetition moved faster; judgment stayed explicit.
The asset was not content alone, but the audience, operating logic and evidence that could survive the people who built it.
Current implementation work in provenance, retrieval and semantic governance.
A local-first system that turns messy corpora into retrievable claims without losing their sources, with uncertain taxonomy kept under operator control.
The system behind this page: one semantic component layer across eight themes and four kinds of surface.
Send the problem in a sentence or two. I will tell you whether a thirty-minute diagnostic is the right next step — and what decision it should resolve.