Operon has a template feature, use it as an entry context point for aigents/staffs

• create a dedicated frontmatter-data.base with all the frontmatter categorized by tables
  • Operon
  • Radial Timeline
  • Digital Garden blogging
  • OKF (cheated a bit by making required type frontmatter to accept multiple values for Radial Timeline "rings"
  • Enhanced Canvas
    adding notes into a canvas will auto add frontmatter canvas: and put a reference.
    { #fdtgff}

Template Example

taskTemplate

Frontmatter

custom plugin Radial Operon sync manipulates frontmatter with *single-stared text*

ID: scn_6dc2b6f1 # RT generated
operonId: 4ot9fcw # Operon generated
datetimeCreated: # set in stone for RT (cant be altered), generated by Operon on create
timestamp: 2026-07-03T11:53:12 # OKF standard key, Operon modified time & RT `When`

type: # OKF required field (must be a string but idc) RT subplots & Operon contexts
  - SOP
Class: Scene # static, must have
Act: 1|2|3|4 ,# represent Do, Defer, Delegate, Draft (a spin of Eisenhower Matrix)
description: ... # RT Synopsis, OKF & Quartz desc, Operon note

*Chapter*: 3a. Unifying frontmatter keys # custom plugin prepend for RT chapter marker
# Custom keys
*canvas*:  # Enhanced Canvas auto populate when notes is refereced
  - "3a. Unifying frontmatter keys.canvas"
Place: RT default location
stakeholder: deliverables

*operonProjectStage*: Default.Working # task status - Operon
*Status*: Working # task status - RT
priority: House # Operon prio:RT convention

*timeSpent*: 3460 # Operon pomodoro
*duration*: 0 hours 57 minutes # custom plugin translate timeSpent (s) to readable time
estimate: 1800 # Operon optional input, will turn 🔴 if > timeSpent

# OPTIONAL, can alter in Kanban or Calender etc
dateScheduled: 2026-07-01
dateStarted: 2026-07-01