Product notes

An AI layer that stays with the conversation.

Forenote is being developed for teams coordinating work across Slack and Microsoft Teams. The primary experience combines ambient attention with conversation: notice a meaningful change, connect it to earlier agreements, bring the consequence forward, and help the team decide what happens next.

What works today

The interactive preview places one persistent Forenote assistant above fictional Atlas conversations. It opens with a useful observation: the security review has moved to October 9, while the launch agreement still says October 8 and release requires sign-off.

You can:

This is an authored, guided simulation with fictional messages, including a new review update and release requirement. Scenario responses are scripted; other sample-memory queries use deterministic matching. There is no model call, background ingestion, OAuth connection or authenticated user. All fixtures are downloaded with the application. The sample profile selector illustrates visibility and is not a security boundary.

The new scenario extends the earlier saved-memory snapshot. The October 9 review estimate belongs to the guided scene; it does not silently rewrite the older sample records or your saved local reviews.

Try the contextual experience · Explore saved sample memory

The record model

Part What it keeps
Decision The agreed wording, review state, and scope
Evidence The exact source messages that support it
Rationale Why the decision was made, with uncertainty made explicit
Commitment The person, next step, and due date when stated
Revision The previous position, current position, and reason for change
Review Who recorded an interpretation and when

A message edit and a changed decision are different events. A newer timestamp alone does not settle a disagreement. When an owner or reason is not established by the source, the product should say so.

The trust model

The following are requirements for the live product, rather than security claims about this preview.

Access before answers. Authenticate the viewer and enforce tenant isolation and current access to each source before retrieval and generation. Ingestion permissions do not automatically give every viewer access to the ingested material.

Evidence before certainty. Extract candidates with supporting source identifiers. Keep a proposal open for review, distinguish interpretation from direct statements, and decline to answer when there is insufficient evidence.

Changes invalidate old answers. When a message is edited, deleted, or becomes inaccessible, invalidate dependent answers and records. Revocation must also affect cached answers, source previews, counts, and suggestions.

History without invented agreement. Local review is a separate event with its own actor and timestamp. It must not masquerade as a Slack message, a Teams message, or an agreement the original speakers never made.

Visible coverage. Show selected channels, import coverage, the last successful synchronization, and any gap. A missing answer must not imply that the team never discussed the topic.

Connecting Slack and Microsoft Teams

The first live pilot is planned around explicitly selected Slack channels and standard Teams channels. Direct messages, external guests, Teams private/shared channels, and organization-wide ingestion need additional access testing before inclusion.

Slack history access depends on token type, scopes, and channel membership. Import limits also depend on the app's distribution model. Historical imports do not reconstruct all earlier edits or deletions. Slack history documentation · Slack message events

Microsoft distinguishes delegated and application permissions, including resource-specific consent. Teams shared-channel membership can have multiple access paths. Live ingestion needs subscription renewal, reconciliation, and effective-access checks. Teams app permissions · Graph message notifications · Channel membership

The path to a live pilot

  1. Validate the decision workflow. Test real coordination problems with delivery leads, compare against their existing tools, and measure time to a correct answer and the effort of review.
  2. Connect a bounded workspace. Register Slack and Microsoft applications, implement consent and identity mapping, ingest selected channels, and preserve real message links.
  3. Add the memory service. Store sources and revisions, enforce access on the server, extract reviewable candidates, and evaluate evidence-backed answers.
  4. Pass the release gates. Test access revocation, deleted sources, conflicting decisions, attribution, unsupported answers, event ordering, tenant isolation, and restore procedures.

The product will earn automation through evaluated results. This preview makes no claims about extraction accuracy, compliance certification, adoption, or time saved.

Preview privacy

The preview does not request access to Slack or Teams. It contains fictional messages and names. Your local edits are stored in this browser using local storage under forenote-ambient-v2 (guided scene) and forenote-demo-v1 (saved memory). They are not sent to a Forenote application server. Avoid entering personal or confidential information into the preview.

Use Replay the scenario to clear the ambient scene’s local note and review. Use Reset demo in saved memory to clear its separate edits. Clearing site data in your browser removes the saved state entirely. The site does not include third-party analytics or tracking scripts. The hosting provider may process ordinary web-request logs under its own policies.

Forenote is a working product name. Name clearance and production privacy terms remain part of preparation for the live pilot.


Last reviewed: September 21, 2026. Back to Forenote · Open the demo