Capabilities
Today & My Work
Read a deterministic daily-focus Context Package for the caller: portfolio attention, related work, cited evidence, coverage, and provenance without turning recommendations into schedule authority.
Interfaces
REST exposes the daily-focus package, the general Context Engine query endpoint used by agents, and confirmed attention-item action recording.
MCP can read the Today & My Work package directly, record confirmed attention-item actions, and still ask natural daily-focus questions through the live Context Engine.
GraphQL exposes the typed myDay query and a confirmed attention-item action mutation backed by the same Context Package and webhook-outbox service as REST.
Confirmed attention-item actions emit attention_item.resolved, attention_item.dismissed, and attention_item.snoozed through the durable webhook outbox.
Required scopes
agent:readAPI key scoperequiredExamples
Get today and my work — view in REST API reference
curl -X GET "https://www.digitalstack360.com/api/v1/me/today" \
-H "Authorization: Bearer $DS_API_KEY"Record a Today attention-item action — view in REST API reference
curl -X POST "https://www.digitalstack360.com/api/v1/me/today/attention-items/b1259ce1-bf47-5a54-8d71-b9b2f4e83ed3/actions" \
-H "Authorization: Bearer $DS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"resolve","note":"Handled during morning standup","context_package_generated_at":"2026-07-15T13:00:00Z","confirm":true}'Query context — view in REST API reference
curl -X POST "https://www.digitalstack360.com/api/v1/context/query" \
-H "Authorization: Bearer $DS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"question":"Why is this project at risk?","project_id":"24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2"}'GraphQL examples
agent:readFetch the caller’s typed daily-focus package with stable attention-item identifiers, coverage, evidence, and the full C1 Context Package.
query MyDay($question: String) {
myDay(question: $question) {
summary
confidenceLevel
generatedAt
attentionItems { id title severity source reason entityKind entityId }
relatedEntities { kind id name drilldownTool }
coverage { source status reason }
contextPackage
}
}agent:readRecord a confirmed resolve/dismiss/snooze action and emit the corresponding webhook outbox event.
mutation RecordMyDayAttentionItemAction($input: MyDayAttentionItemActionInput!) {
recordMyDayAttentionItemAction(input: $input) {
ok
attentionItemId
action
eventType
occurredAt
errors { code message path }
}
}Webhook emits
attention_item.resolvedAvailableA Today & My Work attention item was marked resolved by an explicit caller action.
Resource: attention_item
attention_item_idactionstatusnotesnooze_untilcontext_package_generated_atoccurred_atattention_item.dismissedAvailableA Today & My Work attention item was dismissed as not relevant for the current day.
Resource: attention_item
attention_item_idactionstatusnotesnooze_untilcontext_package_generated_atoccurred_atattention_item.snoozedAvailableA Today & My Work attention item was snoozed until a future timestamp.
Resource: attention_item
attention_item_idactionstatusnotesnooze_untilcontext_package_generated_atoccurred_atAll webhook events use the shared v1 envelope, signed delivery, and minimal payload rule. Fetch by resource id for expanded data.
System boundaries
Systems commonly integrated with this capability. Each row states the boundary and its native status; it does not transfer canonical authority to the connected system.
DigitalStack owns
- • Daily-focus Context Package composition, attention ranking, coverage disclosure, and provenance
- • Workspace-scoped portfolio/project evidence selection for the authenticated caller
- • Confirmed attention-item action facts emitted through the webhook outbox
- • Recommendations and drill-down links to authoritative project/work-item APIs
Source systems own
- • Calendar, chat, ticket, and provider records before they are reflected into governed DigitalStack evidence
- • Human scheduling decisions and commitment changes
- • Source-system issue resolution until the owning domain command is explicitly invoked
Typical integration patterns
DigitalStack Context EngineMCP / AI clientsCalendar / Slack / Teams