A customer-evidence brief
Product research, source references and customer-language findings.
Review: Check the actual source and claim boundaries before using a statement.
Follow a creative into the learning loop.
The retained brief, launch record and exact ad-level read connect one RESIST concept to a real operator decision. You can inspect the work and the limits of the observation together.
Ethos Car Care · 1–20 October 2026 · Actual agency operating work
- Buyer context
Address a coating buyer skeptical of another graphene marketing claim.
- Concept and production
A dawn/afternoon hood scene makes the strategist’s heat-and-water-spot argument visible.
- Exact creative read
The original ad’s 1–12 October observation stays separate from its later scaling copy.
- Operator decision
On 20 October, the operator selected this creative for scaling and iteration. Later production or results are not inferred.
- Ad spend
- $222.19USD · original ad only
- Attributed purchase value
- $445.18USD · 7 attributed purchases
- Recorded ROAS
- 2.00×Attributed value ÷ spend · rounded
1–12 October 2026 · America/Los_Angeles · Native Meta read 2026-11-06. Explicitly requested seven-day click, one-day engaged video and one-day view; impression-date reporting; unified attribution setting disabled. One website pixel purchase action, without summing purchase aliases. The current ad-set setting was captured separately. Daily historical attribution-setting history remains unknown.
Compare the retained historical read
The earlier local series retained USD 5.99 of unknown-bidding spend. Its money tuple matches the later native API read; these are separate observations, not two results to add together. Some October12 rows were fetched October18 before the final click window elapsed. Kept as historical source context; the separate November6 native API observation below confirms the same money tuple after the window.
The selected launch copy matches the dated receipt and the retained ad read. Its authored concept draft stays separate.
Trace the source, review and handoff
| Record | What you can inspect |
|---|---|
Grounded creative direction | The September 30 record retains five knowledge-source hashes, followed by the strategy, authored copy and image brief. |
Actual selected launch copy | The canonical request matches its receipt and the retained ad read. It uses concept 1’s batch message with paragraph spacing normalized; concept 2’s different draft is preserved separately. |
Operator decision | The October 20 read records selection for scaling and iteration. It does not establish causal lift or a later result. |
Image identity | The request records an original PNG hash. The displayed image is the later Meta representation; those are distinct files. |
Read the actual selected launch copy → Compare the separate concept draft →
Packaged code context: edition 2.0.0, released November 4, 2026, from source df2132cce260. This later packaging record does not identify the code checkout that generated the historical sample. Its execution-time revision and complete human-edit attribution remain unbound.
Observed attributed performance, not causal lift or audited profit. The selected launch-copy chain is retained; the exact execution-time source revision and complete human-edit attribution remain unbound. Historical references were not a randomized control. Batch and launch rules differ, and daily historical attribution settings remain unknown. The later packaged code edition is documented separately.
Download the actual selected work package →Source: Retained operational files and dated source records · Private source and exact ad identifiers excluded. Current image retrieval matches the named creative; original-launch image byte identity is unavailable.
Bloomday: Turn the research into a testable acquisition plan.
Research prepared for Bloomday connects buyer language, search demand and prospective offer economics. This was research prepared for the brand, not a client engagement or an achieved campaign result.
October 27, 2026 · research snapshot · Prepared research
- YouTube comments
- 2,216Documented research corpus
- Reddit records
- 414Separate research source; not buyers
- Verified keywords
- 206Search research, not reached audience
Counts stated in the prepared research document. No client engagement, campaign execution or achieved result is claimed. Planning CAC is an assumption, not observed acquisition cost.
Read the prepared research and its scope →Inspect the retained work.
A creative angle keeps its persona and mechanism.
The angle registry records who the argument is for, how it works and where it came from. That gives the strategist a shared direction to carry into a static concept or video scenario.
"required": [
"angle_id",
"name",
"primary_persona_id",
"awareness_level",
"funnel_stage",
"classification",
"angle_archetype",
"primary_trigger",
"mechanism",
"three_rule_pass"
]Selected source fields · snapshot fb7f1d9 · October 22, 2026. This shows the record structure, without a customer record or completed campaign.
| Record | What it retains | Review decision |
|---|---|---|
Persona and buying context | The angle names its primary persona, awareness level and funnel stage. | Check that the direction follows from the actual audience evidence. |
Argument and provenance | The record retains the mechanism and source context; the schema distinguishes spied, page and legacy sources. | Review what supports the argument before adapting it into static or video work. |
Creative handoff | The typed angle is stored alongside a human-readable angle file for subsequent creative work. | Inspect the concept and production brief before separately approving rendering or a launch. |
Source: Committed buyer-repository schema snapshot · Revision fb7f1d9; excerpts are selected fields, not a complete or runnable schema.
See the research and creative demonstration →
The source snapshot explains the workflow’s reviewable records. It makes no customer-result or time-savings claim. Read the related dated system release →
See the connections.
Keep the decision points.
Research informs the work package. Review the package before the account action, then use actual observations to choose the next brief.
Your evidence
Product facts, approved claims, account context and research sources.
Inputs you supplyLicensed source workspace
Meta workflows
- Customer evidence and personas
- Angles, static concepts and scripts
- Rendering, assembly and captions
Review the package
Inspect the source, work product, target account, budget and required approval.
Operator decisionThen, the authorized account action. Preparation, provider rendering, publishing and campaign execution remain distinct steps. Read back what actually changed.
Bring actual observations to the next brief. The separate performance-audit and insights service is not included in this Meta edition.
Inspect the work.
Make the next decision.
Choose a recurring task to standardize first. These descriptions show the handoff your team prepares; the source preview above shows its underlying records.
A static ad package
Copy, image prompts and reviewable creative direction.
Review: Review claims, brand fit, format and intended audience.
A video scenario
A script, shot plan and production inputs for the selected workflow.
Review: Check the idea and script before voiceover, rendering, assembly or captions.
Explore the supported work products
9 of 9 workflow records. Open a title to inspect the next action and boundary.
| Work product | What the package contains |
|---|---|
Research and evidence | 3 shown |
A customer-evidence briefWhat your reviewer checks Check the actual source and claim boundaries before using a statement. Next actionBuild persona context and a supported angle. Keep this boundaryThis page contains no real customer testimony or private research corpus. | Product research, source references and customer-language findings. |
A persona-linked angleWhat your reviewer checks Does the angle follow from research, rather than an invented customer story? Next actionChoose a direction for a creative brief. Keep this boundaryA promising angle is not a tested or profitable winner. | Persona context, angle candidates and the evidence behind the choice. |
A competitor creative readWhat your reviewer checks Distinguish an observed ad from evidence that the ad performs well. Next actionAdapt a supported direction into a persona-linked brief. Keep this boundaryA competitor running an ad is not proof of a profitable winner. | Ad Library references and creative patterns to inspect against your own product facts. |
Packages and production | 4 shown |
A static ad packageWhat your reviewer checks Review claims, brand fit, format and intended audience. Next actionApprove the package before any paid rendering. Keep this boundaryModel and rendering costs use your configured providers. | Copy, image prompts and reviewable creative direction. |
A native creative packageWhat your reviewer checks Review the product claims, persona context and intended destination. Next actionUse the documented native workflow for the approved package. Keep this boundaryThis is not the full Google landing-page suite or a published page. | Native-ad copy, advertorial direction and supporting creative inputs. |
A video scenarioWhat your reviewer checks Check the idea and script before voiceover, rendering, assembly or captions. Next actionUse the documented production steps within the approved budget. Keep this boundaryA storyboard is not a rendered or launched video. | A script, shot plan and production inputs for the selected workflow. |
A rendering and assembly handoffWhat your reviewer checks Confirm asset rights, provider configuration, format and the explicit cost gate. Next actionAuthorize production, then inspect the actual generated output. Keep this boundaryThis descriptive record has not rendered an asset or incurred a provider cost. | Reviewed production inputs for provider rendering, voiceover, assembly and captions. |
Review and account decisions | 2 shown |
A creative reviewWhat your reviewer checks Confirm the source, creative, permissions and next authorized action. Next actionRepair the named findings or approve the next step. Keep this boundaryReview is not a performance verdict or an automatic paid render. | Validation findings and a package a second operator can inspect. |
A Meta launch packageWhat your reviewer checks Check the destination account, creative, budget and granted scope. Next actionAn authorized operator uses the supported launch/management workflow. Keep this boundaryThe separate performance-audit and insights service is not included. | A prepared creative and campaign handoff for the guarded Meta tools. |
Source: Current published product scope · A selection of supported work, not a complete inventory, live execution log or customer result.
The complete workspace.
One full edition.
Blueprints, private source and matching web-agent access together. One full edition for the people who will operate it.
The creative system
- Private source repository and setup guide
- Product, audience and voice-of-customer research
- Persona-linked angle generation
- Static, native and video creative authoring
- Rendering, voiceover, assembly and caption workflows
The operating method
- Blueprints and the full curriculum
- Templates and workflow documentation
- Separate client workspaces and creative registries
- Validation hooks and guarded Meta launch tools
- Lifetime repository updates
Tegra web agent
- Access to the matching Meta Ads web agent
- Browser agent usage billed separately through your wallet
- A focused web interface, not the entire self-hosted repository
Meta Ads AI Agentic System
Full Agentic System · internal business/team use
$19,997USD · one-time
Final sale · applicable tax shown at checkout. Lifetime repository updates. Provider costs, hosting, ad spend and hosted-agent usage are separate. Installation and managed execution are not included.
Know what you buy.
Plan what you run.
Allow 1-2 days for installation and configuration; provider approvals can take longer. This is a planning allowance, not an installation or performance guarantee. Permissions and external approvals can take longer.
Separate access from running costs.
| Surface | Access and cost boundary |
|---|---|
Licensed source Included | Private repository, blueprints, documentation/templates and lifetime repository updates. Your team installs and operates the workspace. |
Matching web agent Access included | A focused hosted interface for the named purchaser. Wallet-based usage is separate; this is not the full repository in a browser. |
Production connections Separate | Your authorized provider accounts, model/rendering usage, data services, hosting and ad spend. Enable only the workflows you configure. |
Managed execution Separate engagement | Installation, account operation and paid consulting are not bundled managed services. Choose a separate service path when Tegra should own delivery. |
Confirm the prerequisites.
- An operator comfortable with Claude Code and PythonYour setup
Name the person who will configure the creative workflow and review its output.
- Python 3.11+, jq and the documented dependenciesYour setup
Use the documented runtime and dependencies for the current repository.
- PostgreSQL and Redis for Meta workflowsYour setup
Plan the local services required by your chosen Meta workflows.
- Your own research/rendering providers and a Meta app/ad account for launch workflowsYour setup
Bring the research/rendering tools and approved account access for production and launch work.
Current edition boundary. The current shipped edition excludes the separate performance-audit/evidence browser and insights service. Performance-reading workflows report missing evidence until that service is available. Internal agency integrations and private client data are not included.
Start with one workflow.
Make the handoff repeatable.
Install one controlled workspace, prepare one useful output, then review it with a second operator. This is a suggested sequence, not a live progress tracker.
- Set upupcoming
Configure one private workspace
Use your named purchaser access and repository setup guide. Preserve individual logins, account permissions and separate client configuration.
- Prepareupcoming
Make one inspectable work product
Prepare one creative brief: connect a real customer insight to an angle, its supporting evidence and a draft concept.
- Reviewupcoming
Repeat the task with a second operator
Retain the source version, actual artifact and review findings. Use the result to decide which recurring task to add next.
Use the released product version.
Lifetime repository updates are included under the current purchase terms. Your implementation owner reviews the release notes, checks compatibility with your configuration and adopts the update in your workspace. Keep the prior source version and review the first output after an update.
Read the public system release history →
Open your purchased product and repository access →Choose expert help when you need a working session.
Use a paid channel consultation or team workflow session for a bounded expert working session. Scope, preparation and price are listed on each consultation page; installation and ongoing channel management are separate engagements.
Evaluate one useful workflow.
Bring the task, your permitted inputs and the person who will run it. Discuss the retained output, review decisions, setup and running costs before a final-sale purchase.
Explore a Meta system demo →Try the narrower browser interface
Explore the matching hosted workflow under its displayed trial and wallet terms. It covers a focused part of the self-hosted system.
Open the matching agent preview →Working in the other channel?
Google Ads AI Agentic System · $19,997 →Read the forwardable buyer brief →
The offer, operator responsibilities, costs and access boundaries in one shareable reference.
Know what you are buying.
What does the one-time price include?
The full agentic edition is $19,997 USD. It includes the licensed private source repository, blueprints and curriculum, the included templates/documentation, matching Tegra web-agent access and lifetime repository updates. It is not a managed account service.
Is running the system free after purchase?
No. Your model/provider accounts, rendering, research/data services, hosting and ad spend have separate costs. The matching Tegra web agent uses wallet-based billing. Access is included; unlimited hosted runs and prepaid credits are not. Use the costs displayed by each provider and start with a bounded workflow.
Can my in-house team or agency use it?
Yes, the purchasing business can use the licensed source internally through authorized team members, including work on client accounts the agency may manage. Use separate named logins and a controlled private workspace. Additional direct Tegra or vendor-repository access needs a named entitlement review. There is no shared-login, automatic colleague access or resale right.
What does setup involve?
Allow 1-2 days for installation and configuration; provider approvals can take longer. An operator comfortable with Claude Code and Python. Python 3.11+, jq and the documented dependencies. PostgreSQL and Redis for Meta workflows. Your own research/rendering providers and a Meta app/ad account for launch workflows. This allowance depends on your operator and external permissions; it is not an instant-setup guarantee.
What is outside the current edition?
The current shipped edition excludes the separate performance-audit/evidence browser and insights service. Performance-reading workflows report missing evidence until that service is available. Internal agency integrations and private client data are not included.
What happens to an existing Blueprint purchase?
Its original documentation, materials and payment history remain available through the existing dashboard. It does not automatically become the full system. Any available paid upgrade must be explicitly reviewed from the purchaser’s authenticated dashboard; the standalone Blueprint edition is no longer sold.
How is the browser preview different from a product demo?
The preview is a narrower hosted-agent workflow with its own trial and usage limits. A product demonstration explains the retained repository, one representative workflow, review decisions, team adoption and operating costs. The source preview shows selected schema fields from a buyer-repository snapshot. It does not show a completed customer output or an observed campaign result.
What support and refund terms apply?
Repository updates and documentation are included. For delivery or access problems contact hello@tegra.co. Installation, operational consulting and ongoing account management are separate engagements; no support response-time SLA is included. Digital-product sales are final under the published terms; review the scope before buying.
Choose your first workflow.
Meta Ads AI Agentic System. One full edition, $19,997 once. Review the included access, setup and costs before purchase. Installation, consultation and ongoing channel management are separate; hosted wallet usage is extra.
Review the full edition →Already bought Blueprint? Your original dashboard materials and purchase history stay available. It does not automatically become the full system. Open your existing access.