An assistant capability handles the owner's recurring work

spec:hq.assistant

Use Case / Behavior · featurescoped floor scoped

Next rung defined waits on 1 unmet clause:

no-blocking-open-questions · Spec has no blocking open question in intent.openQuestions.

Design: no design entries · no pinned declarations · no decisions

specs/hq/assistant.sdp.md

3 open questions and 2 blocking questions; implementation binding none, verifier binding none, and expected-outcome oracle none.

This aspect is unlike the others: it is not software delivery. The owner describes something along the lines of Hermes Agent, with scheduled tasks.

Intent

actor: The owner, and the people who receive what the assistant sends.
problem: Recurring accounting, correspondence and context-gathering work takes the owner's time.
outcome: An assistant capability handles the owner's recurring non-engineering work.
risks: The assistant speaks to clients and accountants in the owner's name, with the owner's context behind it.

Open questions

non-blocking · question.runtime line 27 · specs/hq/assistant.sdp.md:27 · Which runtime carries the assistant?Decider: delegatedProvisional: Something like Hermes Agent, the kind the owner named.
blocking · question.agentPlacement line 30 · specs/hq/assistant.sdp.md:30 · Where does the assistant run, given that it needs HQ's context and faces outward?Decider: delegatedTrigger: the assistant is taken up
blocking · question.sendsAlone line 33 · specs/hq/assistant.sdp.md:33 · What may the assistant send without the owner reading it first?Decider: ownerTrigger: the assistant is taken up

Behavior

rule.scheduled line 39 · specs/hq/assistant.sdp.md:39: The assistant runs the owner's recurring work on schedules.
no example exercises it
rule.accounting line 40 · specs/hq/assistant.sdp.md:40: The assistant prepares the owner's accounting reports and emails the owner's accountants.
no example exercises it
rule.bookmarks line 41 · specs/hq/assistant.sdp.md:41: The assistant checks the owner's Twitter bookmarks, where the owner stores context for projects and research threads, and passes what it finds to HQ's context.
no example exercises it
rule.groupChats line 42 · specs/hq/assistant.sdp.md:42: The assistant answers clients in group chats with the team.
no example exercises it

0 unkeyed rules.

Verification

Verifier bindings

No verifier binding recorded.

Design view

Requirement drawing

Declared verifying examples: no declared verifying example.
Satisfying or referencing units: no recorded binding.
Test or oracle bindings: no recorded binding.

Requirement drawing for spec:hq.assistant

Arrows: refines (declared).

The diagram as text

spec:hq.assistant: An assistant capability handles the owner's recurring work · declared Spec · no satisfying binding
spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work · declared Spec
spec:hq.assistant refines spec:hq.headquarters · declared — the third aspect the owner names

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.

Mermaid source for Requirement drawing for spec:hq.assistant

requirementDiagram
  requirement n0 {
    text: "An assistant capability handles the owner's recurring work · declared Spec · no satisfying binding · spec:hq.assistant"
  }
  requirement n1 {
    text: "HQ plans and designs across every project, and starts the engineering work · declared Spec · spec:hq.headquarters"
  }
  %% claim: declared; reason: the third aspect the owner names
  n0 - refines -> n1

Decisions

No decision record named.

Runtime

No implementation neighborhood recorded.

Runtime observation: not tracked.

Evidence

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.

Impact

Relations of spec:hq.assistant

The diagram as text

spec:hq.assistant: An assistant capability handles the owner's recurring work
spec:hq.context: HQ's private context stays in one place and stays clean
spec:hq.headquarters: HQ plans and designs across every project, and starts the engineering work
spec:hq.assistant dependsOn spec:hq.context · declared — it reads HQ's context and passes what it finds back
spec:hq.assistant refines spec:hq.headquarters · declared — the third aspect the owner names

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Mermaid source for Relations of spec:hq.assistant

flowchart TB
  n0["HQ plans and designs across every project, and starts the engineering work · spec:hq.headquarters"]
  n1["HQ's private context stays in one place and stays clean · spec:hq.context"]
  n2["An assistant capability handles the owner's recurring work · spec:hq.assistant"]
  n2 -->|"dependsOn · declared — it reads HQ's context and passes what it finds back"| n1
  n2 -->|"refines · declared — the third aspect the owner names"| n0

Rests on

refines · spec:hq.headquarters · stated defined, floor ready
dependsOn · spec:hq.context · stated scoped, floor scoped

Rested on by

No Spec rests on this Spec.

Relations

Relation and direction	Other end	Claim	Reason	Exercised keys
dependsOn · outgoing	HQ's private context stays in one place and stays clean `spec:hq.context` · resolves	declared	it reads HQ's context and passes what it finds back	None
refines · outgoing	HQ plans and designs across every project, and starts the engineering work `spec:hq.headquarters` · resolves	declared	the third aspect the owner names	None

Bindings

Implementation binding: none

Design reference: none

Verifier binding: none

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.