Take Interest · Halcyon candidate workspace

What do you need

Request type

Feature A capability you want on a surface Path A repeatable path through the work Agent An agent to run a step for you Other Anything that does not fit the three

Your role

Summary

0 / 120

The problem

0 / 600

Ideal outcome

0 / 600

Context

0 / 600

I understand this is a candidate-workspace demo. My request saves on this device only, no network call is made, and the team cannot promise a response.

How the save is processed

Each step is either a counted check (cyan) or an estimate (cyan, suggested). The final step is a person on the team reading your request.

Check the fields Confirm a summary and the problem are filled, and the acknowledgment is ticked. This is a counted check the form runs every time.

Save the request on this device Your entries are saved together with a local id and a timestamp. They stay on this device and no network call is made.

Add your role and problem Your role label and the problem you described ride along, so the team reads the request in context.

Suggest where it would go An estimate of which team would pick it up, based on the request type. This is a starting point the team can change.

The team reads it A reviewer on the team reads every request and chooses what happens next. We cannot promise a response.

Saved on this device

A request is the start of a path. Every reviewed result on Halcyon points at the same deliverable: one readiness packet, gated by a person.

Open the readiness packet