14 Flower Garden Description Templates

Garden map\nViewpoint: [x]\nBeds/paths: [x]\nHeight/color pattern: [x]\nSeasonal state: [x]\nScent/activity cue: [x]\nScene function: [x]

Plant research\nSpecies/cultivar: [x]\nBloom season: [x]\nToxicity/ecology claim: [x]\nVerified or generalized: [x]

Generic → arranged garden\nGeneric: The garden was colorful.\nLayout: [x]\nDominant pattern: [x]\nRevision: [x]

Continuity\nEntry: [x]\nPath/bed landmark: [x]\nMovement: [x]\nExit/next beat: [x]

Evidence/support and mastery ladder for Flower Garden Description: minimum acceptable → [ ]; strong → [ ]; expert → [ ]; audience/genre constraint → [ ]; evidence or story support → [ ]; boundary that would require a different technique → [ ].

Certainty and expert-exception audit for Flower Garden Description: statement or choice → [ ]; evidence/canon/authority supporting it → [ ]; confidence level → [ ]; uncertainty that must be named → [ ]; expert exception → [ ]; nearest alternative technique → [ ]; why the final choice fits better → [ ].

Purpose-and-verification decision audit for Flower Garden Description: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].

Publication-readiness audit for Flower Garden Description: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].

Provenance and classification audit for Flower Garden Description: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].

Source-record and update audit for Flower Garden Description: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].

Source-ledger and revision-history audit for Flower Garden Description: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].

Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].

Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].

Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].