Name the commercial outcome and the decision the workflow must support.
Auldric workflows
Work starts with a decision.
Choose a workflow by the decision your team needs to make. Each one connects the evidence, choices, review state, and clearly defined next work.
Control
Strategy governs the route.
A prompt can produce an answer without knowing whether the work should exist. Review the objective, audience, positioning, proof, constraints, measures, and decision state before downstream work moves.
Keep the customer, buying pressure, offer, and desired action attached to the route.
Separate source-backed findings, assumptions, contradictions, and discovery gaps.
Show which foundations are ready, partial, missing, or still under review.
Connect an approved decision to a supported output, brief, runbook, or proposed task set.
Inputs
Bring evidence into the route.
Start with the sources the team trusts. Auldric keeps supported findings, assumptions, contradictions, and missing inputs distinct so a reviewer can see what shaped the decision.
Bring documents, calls, notes, plans, performance records, and approved examples the team trusts.
Keep provisional conclusions and heuristics distinct from supported findings.
Turn missing inputs and contradictions into visible questions that could change the decision.
Record what is known, weak, rejected, approved, and still waiting for evidence.
Core routes
Start with the decision.
Choose Marketing Strategy for business-wide direction or GTM for a market, product, offer, readiness, demand, or launch decision. Either route can come first, and each keeps incomplete foundations visible.
Specialist work
Apply an approved strategy.
Brand And Copy Memory and Website Production apply the governing objective, audience, positioning, offer, proof, and desired action. Missing strategic decisions remain visible; Website Production is an emerging route with path-specific execution depth.
Outputs and boundary
Continue approved decisions.
Keep an approved decision connected to the saved output, brief, runbook, or proposed task list that follows. Workspace tasks, workstreams, and connected execution are shown only where those paths are available and verified.
Keep the sources, assumptions, rationale, gaps, review state, and next action together.
Continue an approved decision into a brief or repeatable sequence where that workflow path supports it.
Propose likely owners, dependencies, definition of done, measures, and review points without presenting proposed tasks as assigned work.
Review
Planned measures are not reported results.
Define how a decision should be measured before work begins. Results, objections, source changes, and accepted revisions can update the next cycle only when real signals are available through a supported path.
Name the metric, source, baseline, target, horizon, owner, and decision rule.
Add results only when the source or supported measurement path makes them available.
Separate what changed, what stayed uncertain, and what the signal cannot prove.
Accept, reject, or update the governing decision through a reviewable revision.
Choose the next supported action from the updated evidence and decision state.
Start
Choose the decision in front of you.
Request access and prepare the sources that explain your objective, customers, market, current choices, constraints, and evidence gaps.