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.
04VERIFICATION
Before and after runs against Claude, ChatGPT, Perplexity, Gemini.
Agent Layer — Method / Deliverables
# Knowledge Core — canonical deliverable spec
@type Service
name Knowledge Core
provider 3uild
offer_ref offer.02
format YAML source → signed web document
sections 10 (canon, positioning, offer, audience, proof, voice, comparisons, faq, provenance, agent-directives)
hosting core.[brand].xyz
signing Ed25519 (pipeline pending)
 
# Deliverable pipeline
step.01 Intake — structured claims interview
step.02 Core — 10-section authorship
step.03 Site — domain implementation
step.04 Verification — multi-agent query battery
 
# Re-verification
reverification deferred
rationale priced after first Cores live 12+ months
meanwhile verified 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]
 
sha256 TK — placeholder, replace before ship
signed_by 3uild
signed_at TK — placeholder, replace before ship
key_id TK — placeholder, replace before ship
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.01 seo_agency — does not optimize existing copy for rankings
is_not.02 geo_agency — does not run generative-engine optimization reports
is_not.03 brand_agency — does not produce style guides without canonical records
is_not.04 content_shop — does not write blog posts, ad copy, or marketing decks
 
# authored — four sections only 3uild writes
authored.01 positioning — one-line through one-page, authored not optimized
authored.02 comparisons — named alternatives, honest differences
authored.03 voice — how the brand speaks to both readers
authored.04 agent-directives — instructions for the machine reader
 
claim "3uild writes the canonical version first."
claim_ref positioning.02
 
sha256 TK — placeholder, replace before ship
signed_by 3uild
signed_at TK — placeholder, replace before ship
key_id TK — placeholder, replace before ship
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
@type Service
subject Engagement process
stages 4
invariant stage order, stage outputs, signed artifact
 
# Product-level timelines
timeline.zero 4–6 weeks
timeline.shift 2–4 weeks
rationale Shift 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.label Intake
stage.01.format Structured claims interview
stage.01.client_time 2–3 hours
stage.01.output Verified claims document
stage.01.refuses vibes briefs, mood boards, discovery workshops without source capture
 
# Stage 02 — Authorship
stage.02.label Authorship
stage.02.format 10-section YAML → rendered Core
stage.02.client_time 1 review cycle
stage.02.output Draft Knowledge Core
 
# Stage 03 — Implementation
stage.03.label Implementation
stage.03.format Domain deployment + schema
stage.03.client_time DNS handoff
stage.03.output Live site at core.[brand].xyz
 
# Stage 04 — Verification
stage.04.label Verification
stage.04.format Multi-agent query battery
stage.04.client_time 30-min walkthrough
stage.04.output Signed verification report
 
# Zero-specific parallel work
zero_additions brand strategy, visual identity, website — delivered in parallel with Core stages 02–03
 
# Re-verification
reverification deferred
rationale priced after first Cores live 12+ months
meanwhile verified at production, re-verified on material change at no recurring cost
 
sha256 TK — placeholder, replace before ship
signed_by 3uild
signed_at TK — placeholder, replace before ship
key_id TK — placeholder, replace before ship