support-request see history edit this page

Talks about: , and

Identity

A definition is named by its content, so this address is what a ticket pins and what a consumer checks against:

sha256-84c7f6140fc8cf90ee3a33efde68238cb3eba603b216dfb08aeafcbafc28aa20

Shape

● received
├─▶ triaged            ⊢ category · severity · ✎triager
│   │
│   ├─▶ reproducible   ⊢ category = technical · ⧉repro/
│   └─▶ resolved       ⊢ resolution.ref · (¬category = technical | ⤳reproducible)
│       │
│       ▼ closed ★     ⊢ customer.ack
└─▶ escalated          ⊢ ⏱PT48H · ¬category

Roles to fill

Every role ships empty, so adopting a process never inherits somebody else’s org chart. Name yours with tik roles add <role> <actor>.

Facts it records

PathShape
category[:enum :billing :technical :account :abuse]
customer.ack:boolean
resolution.ref[:string {:min 8}]
severity[:enum :low :normal :high :critical]

Stages

received

Reached immediately — it carries no guards.

Runbook: kb/runbooks/support-request-received.md

triaged

Follows received.

Reached when:

Runbook: kb/runbooks/support-request-triaged.md

escalated

Follows received.

Reached when:

Runbook: kb/runbooks/support-request-escalated.md

reproducible

Follows triaged.

Reached when:

Runbook: kb/runbooks/support-request-reproducible.md

resolved

Follows triaged.

Reached when:

Runbook: kb/runbooks/support-request-resolved.md

closed · sticky

Follows resolved.

Once reached it stays reached: the fold carries it forward, so later evidence cannot take it away.

Reached when:

Runbook: kb/runbooks/support-request-closed.md

Take it

tik adopt processes/support-request.edn```

The definition and its runbooks are copied into your store, and the
publisher's signature travels with them when a key in your `actors`
verifies it.

Read the stages before you adopt: they say who has to sign what,
which is a decision about your organisation.