pub struct Strategy {
pub action: Option<String>,
pub blog: Option<Box<Blog>>,
pub category: Option<String>,
pub enabled: Option<bool>,
pub era: Option<String>,
pub id: Option<String>,
pub principle: Option<String>,
pub source: Option<String>,
pub tags: Option<Vec<String>>,
pub workload: Option<String>,
}Fields§
§action: Option<String>Action is the tactic itself: the thing to go and do, stated imperatively.
blog: Option<Box<Blog>>Blog is the tactic’s long-form explainer; absent for tactics that have none.
category: Option<String>Category is the growth discipline the tactic belongs to — the axis ?category= narrows the corpus on, and one of the facets a caller browses by.
enabled: Option<bool>Enabled is the admin lever. Absent reads as ON; an explicit false drops the tactic from every org-facing corpus read while leaving it in the document.
era: Option<String>Era separates an AI-era tactic (modern) from a classical one (heritage).
id: Option<String>ID is the tactic’s stable slug, unique across the corpus.
principle: Option<String>Principle is the spine slug this tactic files under (a Principle.Slug).
source: Option<String>Source is where the tactic came from — the attribution a reader is owed.
Tags are PRECONDITIONS, not labels — every one must be satisfied by the org’s observed profile before the tactic surfaces, so an untagged tactic is universally applicable. Two vocabularies: stage:<research|formed|launched| activated|scaling> reads the org’s growth stage, has:<capability> reads an observed signal.
workload: Option<String>Workload is how much effort running the tactic costs, so a corpus can be narrowed to what an org has the hands for right now.