Choose what Evodira may read

An enrolled agent that has been given no sources indexes nothing. There is no default folder, no “scan my home directory”, and no discovery pass that reads content in order to decide what to read. A source becomes indexable in exactly two ways: the person at the device approves it, or an administrator pre-approved it as a managed source on the deployment profile (chapter 4).

The console states the standing limits on every surface that touches this, and they are worth committing to memory because people ask:

• Evodira only indexes sources a person approves on their own device, unless an admin has explicitly marked one managed.
• The local agent does not scan browser history, screenshots, microphones or keystrokes.
• Detected secrets and blocked files are redacted on-device and never upload.
• The sync mode controls exactly what may leave the device.
• Central review stays the gate: nothing becomes answerable memory without a human decision.

Before approving anything, you can look at the shape of the disk without reading a single file. discover walks a path and returns a classified folder tree from filesystem metadata alone. No file content is opened.

evodira-local discover ~/Projects --max-depth 4

# Well-known candidates that actually exist on this machine
evodira-local discover-locations

discover-locations lists the catalogue locations present on this device (Desktop, Documents, Downloads, synced drives) with a quick breakdown of what kind of files are in each. It is the fastest way to answer “what would this even find?” before committing to anything.

1. 1

   Grant the folder

   A label is required. It is what appears in the console and in your own device page, so make it something a colleague would recognise.

   Copy

   evodira-local grant ~/Projects/atlas --label 'Atlas project'

   Add --non-recursive to index only the named folder and not its children.

2. 2

   Decide whether knowledge from it may sync

   Granting a folder lets the agent read it on the device. Consenting to sync is a second, separate decision: the standing review the autonomous pack pipeline requires. Give both at once with --consent, or set it afterwards.

   Copy

   # Both decisions at once
   evodira-local grant ~/Projects/atlas --label 'Atlas project' --consent
   
   # Or change consent on an already-approved source
   evodira-local sources
   evodira-local consent <source-id> --sync --mode summary_only

3. 3

   Check what you have approved

   sources lists every approved folder with who chose it: you, a suggestion you agreed to, or your administrator.

   Copy

   evodira-local sources

Catalogue presets, instead of paths

For the well-known locations you can use the preset key and let the agent resolve the path for this operating system.

evodira-local presets list
evodira-local presets add --key documents --label Documents

# What your admin has suggested, and your answer to each
evodira-local presets suggested
evodira-local presets confirm --key desktop
evodira-local presets dismiss --key downloads

A sync mode is a ceiling, set per source and capped by the deployment profile and the workspace policy above it. The lowest ceiling in that stack wins; a source can never exceed its fleet, and a fleet can never exceed the workspace.

Independently of sync mode, the agent refuses categories of content on the device, and the plane refuses them again on arrival.

Detected secrets

Credentials, passwords, private keys, secrets and tokens are detected and redacted before any model sees the text. Deterministic redaction runs first, single-threaded, ahead of everything else.

Blocked patterns

The default policy never opens .env, .env.*, *.pem, *.key, id_rsa, id_ed25519, secrets.*, *.p12 or *.pfx.

Unlisted file types

The policy names the types that may be opened: .md .txt .pdf .docx .csv .xlsx .json .yaml .yml .html by default. Anything not named is never opened.

Above the ceiling

Anything above the source’s approved sync mode, and anything above the profile’s maximum sensitivity.

Held for an admin

Extractions marked confidential or restricted are routed through admin review rather than syncing on the person’s decision alone.

You can read the live rule set on Policies, which states it as commitments in force with a revision stamp, not as a marketing claim.

On a profile whose autonomy ceiling is prepare drafts, the agent builds context packs on its own. If device review is required, each pack waits for you before it leaves.

evodira-local packs list
evodira-local packs approve <pack-id>
evodira-local packs reject <pack-id>

# Send it to an administrator for review before any sync
evodira-local packs approve <pack-id> --admin-review

On a manual ceiling nothing is prepared until you start it:

evodira-local run-once

Approving a pack here is not publication. It leaves the device and lands in the workspace’s review queue, where a steward decides whether it becomes answerable memory. Two gates, and both of them are real.

Some sources sit outside what a profile permits. Rather than silently failing, the agent can raise a source request, the channel a person has for asking that a folder be indexed, and equally for objecting to one that already is.

1. 1

   Raise it from your device page

   Your device lists every folder the agent indexes and who chose it. Against any of them you can say it should not be read, or ask for a new one.

2. 2

   An administrator answers it

   It lands in the Source requests lane of Review. Answering needs source.decide, a permission separate from fleet.manage precisely because approving one widens a data boundary.

3. 3

   You see the answer

   The outcome comes back on your own device page under What you have raised, with what came back. It is the only channel your objection has, and it is not a black hole.