Signal engine

Palette captures selected company activity throughout the week and uses it during the Context Library's weekly generation step. This separates source capture from the readable context people and agents use.

1. Capture selected activity

Organization connections can supply selected events from tools such as Slack, Jira, Linear, GitHub, and Notion. Palette filters and stores relevant events as source material. It does not turn every event into a conclusion as soon as it arrives.

Google Calendar is a personal Connector Gateway connection, not an organization-level Context Library source.

2. Add human context

Team check-ins can add meaning, corrections, or context that tool activity does not contain. This gives the generation step both tool activity and human input to work from.

3. Generate scoped context

Once each week, Palette uses the captured source material to refresh generated pages at the organization, team, and user scope. This is the stage where activity from several sources can be synthesized into plain-English context.

The readable Context Library is therefore refreshed weekly, even though source events can arrive throughout the week.

Confidence and sources

Generated fields can include a model-provided confidence value and source citations. Confidence is not calculated by counting corroborating events, and citations can vary by field.

Next

Read about Context Library scopes, or follow the Context Library quick start.