New signals this week
18
↑ 4 vs. last week
Tuesday, November 3 · Weekly operating view
Good morning, Alderline.
Here’s the work asking for your team’s attention today.
AI-EXECUTED EXTERNAL ACTIONS0in this preview
AI cannot approve its own proposal.
Customer messages and external changes stay blocked until a person reviews them.
Decisions waiting
3
1 overdue for review
Work in progress
7
Across 3 active projects
Loop closed this month
82%
↑ 9 pts from October
Operating pulse
What needs a decision, an owner, or a clear next step.
Needs a decision01
3One has been waiting 4 daysDue this week02
5Across customer and delivery workReady to close03
2Update drafted, needs reviewSignals gaining attention
LConnect Linear projects6 mentions · Slack, portal, customer email
WWeekly team digest4 mentions · portal, Outlook
CFaster CSV import checks3 mentions · portal, Slack
Team queue
Small, concrete next steps.
Decide whether Linear sync belongs in Q4Decision · 6 supporting recordsToday
Review release note for bulk importCustomer update · owner: MeiDraft
Confirm webhook retry behaviorDelivery · owner: SamOn track
Recent activity
Priya grouped two requests under “Integrations”
Mei drafted a customer update for CSV imports
Signal review agent summarized 6 source records
Decisions with evidence
Keep the original customer context attached to each choice.
LShould we build a Linear connection?6 original messages · 4 teams represented · moderate confidence
WWhich digest cadence is useful?4 original messages · weekly is suggested, not confirmed
Workspace notes
Operating context for this sample company.
Alderline is a fictional 10-person product studio. Its sample activity is written as a believable history; it does not represent customer claims or connected account data.
ALNext team review · Thu, Nov 5 · 09:30 UTC
Customer evidence · 18 new this week
Customer signals
Review incoming requests without losing the source, timing, or uncertainty behind them.
| Request | Source | Interest | Status | Owner | Last activity |
|---|
Sample history is synthetic. Selecting a row opens its evidence and review controls.
Bring your history with you · local CSV dry run
Preview a feedback migration.
Start from an export you control. See which history maps cleanly and what needs separate handling before you consider moving anything.
Nothing is uploaded or saved
This page runs in your browser. A selected CSV is read locally for this preview only; it is never sent to VTB Operation. No import is applied, and you can close the tab to clear the preview.
1 · Export from your current tool
Use the source product’s own CSV export.
2 · Choose a CSV file
Maximum 2 MB · preview stays on this device
The dry run detects missing titles and repeated titles. It does not merge, overwrite, or import records.
Dry-run preview
Field mapping
What this export does not carry
| Source title | Vote count | Status | Import check |
|---|
Delivery · 3 active projects
Projects & work
Move approved decisions into owned work, with a simple view of progress and blockers.
External platforms · scoped access
Connections
Choose the systems VTB Operation may read. Every integration starts with a narrow, reviewable permission set.
Preview environment: No accounts are connected. Buttons open setup previews only; they do not start OAuth or make API calls. Permission scopes must be confirmed against each provider before a live rollout.
For engineers · event contract preview
A concrete data shape to review before a live connector exists.
No product API, webhook endpoint, OAuth app, SDK, or sandbox key is available yet. The example below is a proposed read-only event envelope, not a request you can send. This preview does not call any provider or VTB endpoint.
Example feedback event
{
"event": "feedback.received",
"event_id": "evt_sample_001",
"occurred_at": "2026-11-03T10:26:00Z",
"source": { "kind": "portal", "record_id": "sample_184" },
"content": { "title": "Connect Linear projects", "body": "We copy this every Friday." },
"evidence": { "url": "https://example.invalid/sample/184", "votes": 42 },
"provenance": { "synthetic": true }
}Before a live key is issued
- Publish the API schema and versioning policy.
- Define read-only scopes and tenant isolation.
- Document webhook signing, retries, and deletion behavior.
- Provide a test workspace and revocable sandbox credentials.
A request for these items is a real founder follow-up; it does not create or issue a key.
SYNTHETIC EXAMPLE · HOW THE AGENT HELPS
6
→original messages
1
review proposal
Six separate requests from Slack, Outlook, and the customer portal are grouped into “Connect Linear projects.” Every source stays intact; the agent only suggests an internal theme for a person to review.
“We copy it every Friday”“Keep the source link attached”“Four versions of the same ask”Human approval required · no external action
Agentic workflow · human decision gate
Agent review
Automation can collect, organize, and prepare. A person controls every consequential change.
3 proposals awaiting review
Execution is disabled here. This workspace preview can record sample review decisions in local page state. It cannot write to Slack, project trackers, email, billing, or customer records.
Review queue
Newest first · proposals are not actions
Proposal detail
Inspect evidence, scope, confidence, and policy before deciding.
Company signals · 30-day view
Analytics
Understand how requests move through review and into shipped work. Sample metrics are illustrative.
Feedback reviewed
74
↑ 12% vs. previous 30 days
Median time to decision
2.4d
↓ 0.6d from previous period
Updates sent
11
To people who shared feedback
Unlinked signals
8
Need a decision or a reason to defer
Signals to decisionsWeekly flow · sample period ending Nov 2
30 daysReviewedReceived
Review pathWhere incoming signals stand now
Received
Grouped
Decided
Planned
Closed loop
Where to focus
Eight requests have no decision or defer reason. A short review can clarify the next step before more signals arrive.
Controls & activity · for a small team or a larger one
Choose what the AI can do.
Start with selected, read-only sources and suggestions. Keep customer messages and sensitive changes behind your team’s explicit approval.
Simple by default; detailed when needed. A small team can leave these safe defaults in place. Teams with stricter processes can scope access, inspect each change, and export the decision history. These controls are a working preview and do not govern a connected account.
What the agent may do
Each switch represents one clear permission boundary.
Decision history
Sample change log · available for team oversight.
Proposal reviewed · “Weekly team digest” kept for separate review
Connector scope viewed · Slack selected channels, read only
Draft updated · CSV import customer note
Policy evaluation · external email blocked by default
Permission levels
Three plain rules, with a clear human checkpoint as impact increases.
Read
Look at only the sources your team selects; no changes are made.
Prepare
Organize information and draft internal work. A person reviews before it changes the shared workspace.
Act outside the workspace
Messages, publishing, billing, deletion, and access changes stay off or require a separate human decision.
Workspace administration
Workspace settings
Manage the workspace profile, team access, notifications, and sample data preferences.
OWNER ACCESS