Frameworks

Make nine interdependent authority layers inspectable.

Owner

Joshua H. White

Decision it clarifies

See how strategy, identity, visibility, authority, experience, intelligence, systems, execution, and improvement affect one another.

Evidence required

Business decisions, canonical facts, discovery observations, claims and sources, audience journeys, systems, delivery records, and measured learning.

Outputs

Layer map, dependency path, evidence request, and target-state questions.

Limits

It does not create a universal score, prove causation, guarantee visibility, or replace the evidence required inside each layer.

Dependencies

Current facts, owned decisions, and evidence for every affected layer.

Appropriate use

Framing cross-functional authority and architecture decisions.

Inappropriate use

Scoring organizations or promising search and AI outcomes.

Change control

Layer definitions and dependencies change only through a recorded method review.

Separate the conditions that shape discoverability.

Owner

Joshua H. White

Decision it clarifies

Separate the technical, entity, semantic, search, AI, authority, and market conditions that make an organization discoverable.

Evidence required

Crawl and index behavior, provider observations, source ownership, entity facts, audience demand, retrieval context, and distribution pathways.

Outputs

Discovery-condition map and observation plan.

Limits

It does not imply control over search or AI providers, rankings, citations, recommendations, or demand.

Dependencies

Canonical identity, source ownership, and dated provider observations.

Appropriate use

Diagnosing visibility conditions before choosing tactics.

Inappropriate use

Treating one provider answer as a stable market measure.

Change control

New provider surfaces require dated observations before altering the model.

Translate an authority blueprint into an owned operating cycle.

Owner

Joshua H. White

Decision it clarifies

Turn a one-time authority blueprint into observation, prioritization, delivery, measurement, and correction.

Evidence required

Decision rights, backlog criteria, release records, measurements, defects, review dates, and approved changes.

Outputs

Operating cadence, decision rights, review gates, and improvement loop.

Limits

It does not prove that every activity creates authority or that one cadence fits every organization.

Dependencies

Approved blueprint, owners, measurements, and change authority.

Appropriate use

Operating an approved authority program.

Inappropriate use

Substituting a process diagram for real ownership.

Change control

Cadence and responsibilities change through an owned operating review.

Classify AI visibility observations without inflating them.

Owner

Joshua H. White

Decision it clarifies

Distinguish a mention from a cited source, recommendation, omission, contradiction, or repeatable observation.

Evidence required

Provider and model surface, prompt, locale, date, answer, citations, source conditions, repeat runs, and limitations.

Outputs

Observation record, claim class, uncertainty, and next verification action.

Limits

It does not turn a provider response into a stable fact, ranking, or guaranteed future answer.

Dependencies

Reproducible observation conditions and current provider documentation.

Appropriate use

Bounded AI visibility observation and evidence review.

Inappropriate use

Creating a score or citation guarantee.

Change control

Observation classes change when provider behavior or the recording method changes.

Connect entities, questions, evidence, services, and maintained content.

Owner

Joshua H. White

Decision it clarifies

Connect topics, entities, questions, evidence, services, and maintained content into a coherent knowledge system.

Evidence required

Canonical entity records, topic ownership, audience questions, claim sources, content relationships, internal links, and refresh history.

Outputs

Entity-topic map, content ownership, and refresh requirements.

Limits

It does not manufacture expertise or authority where credible evidence does not exist.

Dependencies

Canonical facts, evidence ownership, and maintained content.

Appropriate use

Designing an evidence-linked knowledge system.

Inappropriate use

Generating commodity content at scale.

Change control

Relationships change when source records, audience needs, or maintained content change.

Connect audience questions to useful evidence, services, and decisions.

Owner

Joshua H. White

Decision it clarifies

Connect a buyer's question to the information, evidence, service, and next decision that can actually help.

Evidence required

Audience questions, demand, journey behavior, content, proof, service fit, conversion events, and outcome definitions.

Outputs

Question-to-evidence path and next-action map.

Limits

It does not treat every search as purchase intent or claim that content alone causes an outcome.

Dependencies

Audience evidence, current service architecture, and valid next actions.

Appropriate use

Designing question-led content and decision paths.

Inappropriate use

Forcing every query into a sales conversion.

Change control

Question classes change when audience evidence or service architecture changes.

Inspect trust as layered evidence rather than presentation alone.

Owner

Joshua H. White

Decision it clarifies

Identify which layers of integrity, identity, clarity, evidence, experience, and corroboration are weakening trust.

Evidence required

Technical behavior, canonical facts, claims, disclosures, usability, accessibility, security signals, independent sources, and objections.

Outputs

Trust dependency map and evidence gaps.

Limits

It does not reduce trust to one number or substitute presentation for integrity and corroboration.

Dependencies

Current behavior, truthful claims, usable experience, and independent evidence.

Appropriate use

Inspecting where a trust decision is unsupported.

Inappropriate use

Publishing a self-awarded trust score.

Change control

Layers change only when evidence shows a material dependency or failure mode.

Separate discovery, trust, recommendation, selection, and action.

Owner

Joshua H. White

Decision it clarifies

See how discovery, trust, recommendation, selection, and action contribute differently to a business decision.

Evidence required

Journey research, source and referral data, provider observations, content interactions, evaluation behavior, conversion definitions, and attribution limits.

Outputs

Influence-stage map, measurement boundary, and test plan.

Limits

It does not assign unsupported causation to a ranking, mention, citation, or touchpoint.

Dependencies

Defined decision journey, trustworthy measurements, and attribution limits.

Appropriate use

Planning measurement around a real decision journey.

Inappropriate use

Claiming one signal caused revenue or selection.

Change control

Stages change when the actual decision journey or evidence quality changes.