Inspect the logic, not a performance claim.

A positioning brief should give the website, sales conversation, proposal, and team one stable commercial story. This is the current Field Theory brief in compact form.

Buyer

Established service and family businesses whose reputation has outgrown the system presenting and selling the work.

Visible problem

An unclear offer, dated website, weak proof, slow intake, or inconsistent follow-up makes good work harder to understand and buy.

Promise

Align the message, evidence, digital front door, and commercial handoffs so the buying path holds together.

Method

Trace Signal, Access, Flow, and Force; locate the primary constraint; rebuild the smallest coherent set of dependencies.

Proof rule

Use observable facts, public artifacts, tested behavior, and permissioned outcomes. Label demonstrations and hypotheses plainly.

Boundary

No guaranteed rankings, traffic, conversion, revenue, or results. No scraped outreach, automatic direct messages, or synthetic client stories.

A useful path resolves uncertainty in sequence. It does not force every visitor into the same call to action or hide the useful answer behind a form.

1. 01RecognizeThe owner sees a concrete symptom in plain language and can identify whether the practice is relevant.
2. 02InspectThe buyer reviews the method, engagement shapes, Field Notes, public artifacts, and owned-system work.
3. 03MapThe free Field Friction Map gives a private, immediate directional result without collecting contact information.
4. 04InquireA high-context project inquiry captures the problem, timing, prior attempts, and source without claiming it was submitted.
5. 05ReviewHuman judgment determines whether a useful conversation is warranted before any private scheduling path is offered.

This target-state blueprint was created during Field Theory's own rebuild. It is not live intake architecture. The current project inquiry opens an email draft and does not store a submission. A future durable system should implement and verify the states below before claiming receipt.

1. 01 · Validate

   Reject malformed, oversized, automated, or incomplete submissions before any write.

2. 02 · Commit

   Write the inquiry and its outbox event in one transaction. Only then may the interface confirm receipt.

3. 03 · Notify

   Process internal notice and acknowledgment from the outbox with retries and idempotency.

4. 04 · Review

   A person assesses fit, context, timing, and the most useful response.

5. 05 · Route

   Qualified inquiries receive a private scheduling path. Others receive a direct, useful close or next resource.

6. 06 · Learn

   Record booking, held meeting, qualification, proposal, outcome, source, and reason codes in one system of record.

• A database failure must never produce a success message.
• A notification failure must leave a retryable record and visible alert.
• A browser retry must not create a duplicate inquiry.
• Contact details and form answers must stay out of analytics and URLs.
• Scheduling stays private until human fit review.

This is the operating path used to move a Field Note from a real buyer question to an approved, tested, and observable public page. The build and claim gates are active. Publication remains operator-controlled. Search and engagement review is limited to the data sources that are actually connected.

1. 01SelectChoose one real buyer question from conversations, search evidence, or an observed system pattern.Operator decision
2. 02DraftWrite the complete useful answer, source consequential claims, and define the relevant next path.Human-authored release candidate
3. 03ReviewCheck evidence, permissions, privacy, client references, unsupported promises, and search intent.Human approval required
4. 04VerifyRun the production build, route tests, metadata checks, claim safeguards, and server-rendered smoke test.Automated release gate
5. 05PublishRelease only the approved artifact, then verify the live URL, crawl signals, links, and error behavior.Operator-controlled publication
6. 06LearnReview available search and engagement evidence after 14 and 42 days, clearly marking any unavailable data.Partly blocked until measurement is connected

• No automatic publication of an unfinished or unapproved draft.
• No client name, quote, result, or private artifact without documented permission.
• No generated distribution message is sent before Anderson reviews it.
• A failed build or integrity check blocks the release candidate.
• Unavailable analytics or search data is reported as unavailable, not estimated.