Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

job / candidate

Post-performance records — forms

The distinct forms record for Post-performance records. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
job:rebecca:post-performance-records
Parent lifecycle
candidate
Page lane
package
Lane lifecycle
proposed
Owner
Rebecca
Owner role
Social media operating agent
Owner status
PROPOSED
Qualification result
NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Record identity

Bind the post-performance record to a specific source and revision.

  • Record title
  • Canonical record ID
  • Origin
  • Source locator
  • Source SHA-256 if available
  • Provenance note
  • Revision number
  • Lifecycle
  • Tags
  • Linked campaign or project
  • Owner agent
  • Human reviewer

Performance event

Describe what was observed without implying a live provider connection.

  • Channel name as supplied by a human
  • Account label as supplied by a human
  • Post or draft reference
  • Event or observation date and time
  • Observation window start
  • Observation window end
  • Declared source of metrics
  • Metric name
  • Metric value
  • Unit
  • Comparison baseline
  • Measurement limitations
  • Attachment or file reference

Assessment and record outputs

Turn observations into bounded internal findings and follow-up work.

  • Observed outcome
  • Evidence citation
  • Confidence or evidence quality
  • What is known
  • What is unknown
  • Proposed interpretation
  • Alternative explanation
  • Recommended next action
  • Follow-up owner
  • Due date
  • Priority
  • Recurrence candidate
  • Human-review signal

Approval and publication boundary

Prevent unapproved public communication or external effects.

  • Approval state
  • Approver identity
  • Approval timestamp
  • Approved scope
  • Held scope
  • Publication request text
  • Account authorization evidence
  • Publication evidence
  • Direct-message commitment present
  • Paid-promotion request present
  • Reason for hold
  • Receipt reference

Accessible state contract

  • Every field requires a visible and programmatic label.
  • Required and optional fields must be stated in text.
  • Invalid entries require an actionable message linked to the field.
  • Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the docs_urls lane and remain separate from the primary operating form.

Post identity and ownership

Identify the communication and assign record ownership without claiming that an account or provider is connected.

  • draft record ID
  • post-performance record ID
  • owner agent: Rebecca
  • business page or account label
  • channel label
  • campaign or project label
  • operator or reviewer name
  • record status

Publication context

Capture the approved or held publication context and distinguish proposed, approved, published, and held states.

  • approval record ID
  • approval state
  • approval decision timestamp
  • approved copy revision ID
  • intended publication date and time
  • actual publication date and time, if supplied
  • publication state: proposed, approved, published, failed, or held
  • publication receipt ID, if supplied
  • account approval confirmation

Performance evidence

Record source-labelled observations after publication without inventing customer proof or unsupported outcomes.

  • observation window start
  • observation window end
  • reported performance measures
  • measure values and units
  • source locator for each measure
  • source capture timestamp
  • customer proof reference, if any
  • evidence confidence or review note
  • unknown or unavailable measures

Review and follow-up

Route conclusions and commitments through human review and preserve unresolved work.

  • reviewer decision
  • decision rationale
  • follow-up task
  • due date
  • recurrence candidate flag
  • direct-message commitment flag
  • paid-promotion flag
  • account-connection issue flag
  • next review owner
  • notes and revision summary

Required or proposed record references

No record existence is asserted by this documentation page.

  • Source-labelled post or campaign record with canonical ID, origin, source locator, source SHA-256 when available, provenance, revision, lifecycle, tags, links, and attachments
  • Performance observation record containing the observation window, source context, measured values, and limitations
  • Draft ledger entry linked to the post, channel, revision, and reviewer
  • Approval record with Needs review, Approved, or Held state and preserved receipt
  • Publication-receipt record, held unless a human supplies evidence of an external publication
  • Account-connection record, held unless separately authorized and evidenced
  • Customer-proof evidence record, required before any customer-result claim; otherwise mark claim unsupported
  • Direct-message commitment record for any proposed response or promise
  • Agent-log entry recording Rebecca's work, authority boundary, inputs, outputs, and unresolved failures
  • Draft record with source context and revision
  • Approval record showing Needs review, Approved, or Held
  • Account and channel reference, without implying an active connection
  • Publication receipt or held-outcome receipt
  • Post-performance record linked to the draft, approval, and receipt
  • Evidence references for any reported result
  • Agent log entry preserving authority and current state

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • agents/index.html#rebecca
  • source_record:job:rebecca:post-performance-records
  • Observed native contract: PointGuard persistent context surface; specialist apps remain execution and canonical-record owners.
  • Observed native contract: Notebook records preserve canonical IDs, provenance, source locators, revisions, lifecycle, tags, links, and attachments.
  • Observed native contract: NotebookTodoPayload supports due dates, priority, recurrence candidate, completion state, tags, revisions, and deadline views.
  • Observed native contract: provider, credential, database, customer, publication, and production effects are held.
  • App routes supplied for Notebook approvals, messages, projects, agent logs, field guides, files, notes, to-dos, and Business messages.
  • source_record.record_type=job
  • source_record.record_id=job:rebecca:post-performance-records
  • source_record.owner_agent=Rebecca
  • source_record.existing_tools=Social curator; Content calendar; Draft ledger; Approval queue
  • source_record.existing_guides=Brand voice; Channel rules; Campaign packets; Publication receipts
  • source_record.principal_gates=Every public post; Account connections; Paid promotion; Direct-message commitments
  • source_record.never_rules=Self-authorize publication; Invent customer proof; Use an unapproved account
  • OBSERVED_NATIVE_CONTRACT.deadlines
  • OBSERVED_NATIVE_CONTRACT.records
  • OBSERVED_NATIVE_CONTRACT.pointguard
  • OBSERVED_NATIVE_CONTRACT.web_boundary