One local place for the whole job

Bring the outcome.Kestrel handles the work.

Choose a project and say what done looks like. Kestrel can inspect, build, research, run, and verify—then pause before consequential action.

See one verified workflow Read the safety model
Development preview · mocked connectors · no signed public download yet
Kestrelwaiting for approval
Teacher emailFriday or Monday?

Choose a date for the Algebra II test.

Friday · 3:30 PMSwim practiceVerified recurring event
RecommendationMonday looks better.

Friday is compressed by swim. Monday leaves the weekend open to study.

  1. 01Notice
  2. 02Retrieve
  3. 03Plan
  4. 04Approve
  5. 05Act
  6. 06Verify
01 / ONE COMPLETE DECISION

A request arrives.A reviewable answer is already waiting.

A teacher offered Friday or Monday. Kestrel checked the calendar, found Friday swim, protected the weekend for study, and prepared the exact changes—without sending them.

  1. ✓Email read
  2. ✓Options extracted
  3. ✓Calendar compared
  4. ✓Monday recommended
  5. ✓Reply drafted
  6. ✓Event prepared
  7. 07Approval requested
Kestrelwaiting for approval
Teacher emailFriday or Monday?

Choose a date for the Algebra II test.

Friday · 3:30 PMSwim practiceVerified recurring event
RecommendationMonday looks better.

Friday is compressed by swim. Monday leaves the weekend open to study.

02 / CONTEXT WITH A BOUNDARY

Remember less.Use the part that changes the answer.

When a DJI controller reports a connection problem, generic troubleshooting starts with a cable and restart. Kestrel can avoid repeating steps already tried and weigh the phone's developer beta instead.

"Because the phone still charges, DJI Fly launches, and another cable already failed, software compatibility now outranks a dead controller."
Retrieval scopeDecision-changing context onlyUnrelated personal memory stays outside the working context.
DJI Mini 3phone controlleriPhone 16 ProiOS developer betaphone still chargesDJI Fly launchessecond cable testedrestart attemptedRC not connected
Relevant context only

Software compatibility now ranks above a dead controller or cable.

03 / CONTROL THAT STAYS VISIBLE

Autonomy stops where consequence starts.

Every action receives a policy level. External communication pauses by default. Sensitive submissions and high-consequence changes always require stronger review.

  1. 0
    Read and prepareNo external side effect
  2. 1
    Reversible local workConfigurable approval
  3. 2
    External communicationApproval by default
  4. 3
    Sensitive submissionExplicit review every time
  5. 4
    High consequenceStrong confirmation
Try the local approval state
Local approval previewLevel 2
Reason

Monday avoids Friday swim and keeps the weekend open.

Exact changes

Preview 1 reply · preview 1 event · prepare 2 study blocks

Review the exact reply and calendar change. Nothing has been sent.

This interaction changes only the preview in your browser. It has no agent endpoint.

04 / ONE GRAMMAR, DIFFERENT WORK

The plan changes.The safety grammar does not.

Kestrel uses available tools and installable skills to plan unfamiliar work. Each example below is a task shape—not a claim of a dedicated production integration.

01

A repository is shared

Inspect the project, plan the change, implement it, and run the relevant checks.

Local changes remain reviewable.
02

A folder is provided

Understand the contents, apply the requested transformation, and organize the outputs.

Access stays scoped to the selected folder.
03

A scheduling request arrives

Compare commitments, recommend an option, and prepare the reply and event.

External communication waits for approval.
04

The task is unfamiliar

Discover available tools and skills, construct a plan, and verify the result.

Missing capability is reported, not invented.
05 / LOCAL-FIRST BY ARCHITECTURE

Personal context has a perimeter.

The current vertical slice implements these controls. A production release remains gated on packaged security, signing, and hardware verification.

01

Encrypted memory fields

AES-256-GCM protects stored content. The database key stays in macOS secure storage and never enters the renderer.

02

Sandboxed interface

No Node integration, raw filesystem, or database handle. IPC remains narrow and schema-validated.

03

Scoped permissions

Selected folders are allowlisted. Accessibility, screen recording, and Apple Events stay off until needed.

04

Untrusted-content boundary

Email and web content remain data. Deterministic policy—not text inside that content—governs tools.

05

Inspectable activity

Observation, context, proposal, approval, execution, and verification appear as separate audit events.

06

Deletable context

The architecture includes source inspection, correction, deletion, and channel-separated storage.

06 / RELEASE READINESS

The development app is real.The public release is not ready to pretend.

A signed download stays unavailable until the distribution gates are complete. The website will not turn pending infrastructure into a fake call to action.

Current version0.1.0 development

  • ReadyAd-hoc-signed Apple Silicon development app
  • PendingDeveloper ID signing and notarization
  • PendingGatekeeper verification on packaged artifacts
  • ReadyApple Silicon arm64 architecture verification
  • PendingPublic download, manifest, checksums, and update host