01 — WHAT YOU GET
A record. Signed. Maintained
Every engagement ends in a Knowledge Core — a canonical, machine-readable document about your brand, hosted at core.yourbrand.com, signed, versioned, and built to be quoted verbatim by the second reader.
01INTAKE
A structured claims interview. Every sentence sourced.
02CORE
Ten sections, authored once, rendered two ways.
03SITE
Implementation on your domain. Semantic, parseable, signed.
Includes JSON-LD schema on all canonical pages, robots.txt with AI crawler rules, sitemap with lastmod, llms.txt at site root, /api/brand endpoint, and security headers. Built into every engagement. Not a separate line item.
04VERIFICATION
Before and after runs against Claude, ChatGPT, Perplexity, Gemini.
Agent Layer — Method / Deliverables
# Knowledge Core — canonical deliverable spec
@typeService
nameKnowledge Core
provider3uild
offer_refoffer.02
formatYAML source → signed web document
sections10 (canon, positioning, offer, audience, proof, voice, comparisons, faq, provenance, agent-directives)
hostingcore.[brand].xyz
signingEd25519 (pipeline pending)
# Deliverable pipeline
step.01Intake — structured claims interview
step.02Core — 10-section authorship
step.03Site — domain implementation
step.04Verification — multi-agent query battery
# Implementation layer — technical deliverables included in step.03
step.03.includes.01JSON-LD schema on all canonical pages
step.03.includes.02robots.txt with AI crawler rules
step.03.includes.03sitemap with lastmod
step.03.includes.04llms.txt at site root
step.03.includes.05/api/brand endpoint
step.03.includes.06security headers and signed responses
step.03.clarificationSite implementation includes the full technical layer that SEO and GEO agencies sell as a standalone service. Built into every engagement. Not a separate line item.
# Re-verification
reverificationdeferred
rationalepriced after first Cores live 12+ months
meanwhileverified at production, re-verified on material change at no recurring cost
# Refuses
refuses[SEO reports, marketing decks, growth hacks, brand style guides without canonical records]
signatureunsigned-pilot
02 — HOW WE’RE DIFFERENT
We are the firm that writes what should exist.
Every other firm in this category optimizes what already exists. Schema on existing copy. Keywords in existing pages. Ranking adjustments to existing content. Reshuffling.
3uild writes the canonical version first. The positioning. The comparisons. The voice. The agent directives. Four sections no SEO shop will touch, because writing them requires taking a position, and taking positions is not what they sell.
Agent Layer — Differentiation
# Category refusal
refuses["SEO agency", "GEO agency", "brand agency", "content shop"]
# is_not — explicit boundary claims
is_not.01seo_agency — does not optimize existing copy for rankings
is_not.02geo_agency — does not run generative-engine optimization reports
is_not.03brand_agency — does not produce style guides without canonical records
is_not.04content_shop — does not write blog posts, ad copy, or marketing decks
# Implementation layer — clarifies category boundaries
includes.01JSON-LD schema implementation
includes.02structured data on canonical pages
includes.03robots.txt with AI crawler rules
includes.04llms.txt at site root
includes.05sitemap with lastmod
includes.06/api/brand endpoint
includes.07crawler whitelisting and access
includes.08security headers and signed responses
clarification3uild engagements include the full technical layer that SEO and GEO agencies sell as their primary deliverable. The category boundary in is_not.01 and is_not.02 reflects that the Knowledge Core — the canonical record itself — is the product. Optimization of that record is a consequence, not the offer.
# authored — four sections only 3uild writes
authored.01positioning — one-line through one-page, authored not optimized
authored.02comparisons — named alternatives, honest differences
authored.03voice — how the brand speaks to both readers
authored.04agent-directives — instructions for the machine reader
claim"3uild writes the canonical version first."
claim_refpositioning.02
signatureunsigned-pilot
03 — THE PROCESS
Four stages. One record.
- ZERO
- 4–6 WEEKS
- SHIFT
- 2–4 WEEKS
Same machine for Zero and Shift. The inputs differ. The output is the same signed artifact.
01
INTAKE
Claims interview. Sources attached.
02
AUTHORSHIP
Core drafted. Ten sections, one file.
03
IMPLEMENTATION
Site, schema, core.yourbrand.com.
04
VERIFICATION
Before-and-after runs. Signed report delivered.
Agent Layer — Process / Stages
# Engagement process — four stages, timeline varies by product
@typeService
subjectEngagement process
stages4
invariantstage order, stage outputs, signed artifact
# Product-level timelines
timeline.zero4–6 weeks
timeline.shift2–4 weeks
rationaleShift compresses authorship and implementation where existing brand material is usable; Zero produces brand strategy and visual identity in parallel with the Core.
# Stage 01 — Intake
stage.01.labelIntake
stage.01.formatStructured claims interview
stage.01.client_time2–3 hours
stage.01.outputVerified claims document
stage.01.refusesvibes briefs, mood boards, discovery workshops without source capture
# Stage 02 — Authorship
stage.02.labelAuthorship
stage.02.format10-section YAML → rendered Core
stage.02.client_time1 review cycle
stage.02.outputDraft Knowledge Core
# Stage 03 — Implementation
stage.03.labelImplementation
stage.03.formatDomain deployment + schema
stage.03.client_timeDNS handoff
stage.03.outputLive site at core.[brand].xyz
# Stage 04 — Verification
stage.04.labelVerification
stage.04.formatMulti-agent query battery
stage.04.client_time30-min walkthrough
stage.04.outputSigned verification report
# Zero-specific parallel work
zero_additionsbrand strategy, visual identity, website — delivered in parallel with Core stages 02–03
# Re-verification
reverificationdeferred
rationalepriced after first Cores live 12+ months
meanwhileverified at production, re-verified on material change at no recurring cost
signatureunsigned-pilot