Inventory · Create · Writing & Content
Scored brickyard inventory of demand-and-trust touchpoints
I get a structured brickyard: every touchpoint sorted into the five areas (online presence, content, offerings, customers/partners/influencers, internal team) and rated on three fixed dimensions, ready to assemble into a journey.
You receive: A JSON object { product: string, bricks: [ { name, area (enum: online_presence|content|offerings|ecosystem|internal_team), create_demand (enum: yes|somewhat|no|na), build_trust (enum: yes|somewhat|no|na), potential_impact (enum: positive|neutral|negative|na), status (enum: ready|cracked|missing) } ], area_counts: {..per area..} }
Part of Grow Partnerships
Opens soon
This objective is verified and ready. It opens soon, once sign-in and payments are live.
Deliverable interface
The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.
{
"buyerParamKeys": [
"require_ecosystem_partner"
],
"checkNames": [
"format_parses",
"bricks_present",
"area_enum",
"demand_enum",
"trust_enum",
"impact_enum",
"status_enum",
"five_areas_covered",
"per_area_floor",
"per_area_cap",
"unique_names",
"partner_required",
"area_counts_match"
],
"constants": {},
"deliverableLabel": "brickyard_inventory",
"documentKeys": [
"area",
"area_counts",
"bricks",
"build_trust",
"create_demand",
"name",
"potential_impact",
"status"
],
"enumLiterals": [
[
"online_presence",
"content",
"offerings",
"ecosystem",
"internal_team"
],
[
"positive",
"neutral",
"negative",
"na"
],
[
"ready",
"cracked",
"missing"
],
[
"yes",
"somewhat",
"no",
"na"
]
],
"submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
"tier": "doc-validator"
}Get early access to STUD the day it goes live.