URI policies
The path rules brain-core's manifest seeds into its own data and package areas, and its one safety policy.
brain-core declares two uriPolicies baselines in its manifest. They are seeded
into a source's persisted policy when the source is first attached, and from
then on that persisted policy is authoritative — see
Sources. The rule shape,
the merge, and who a privileged row admits are defined once, on
package-system URI policies (the requester rule:
Naming the requester).
Editing a source's rules needs sources.policy — in the Sources panel, through
the policies/uri route, or with the
manage-uri-policy skill.
data://<self>/** — brain-core's data area
The default is read and write, no exec. On top of it:
| Path | Effect |
|---|---|
logs and logs/** | Not readable (and logs/** not writable) by default; a privileged override row restores read |
_pending/** | The pending-change journal and its baselines: no read, write or exec by default; a privileged override row restores read and write |
That is why the review journal behind Changes
is readable only by privileged roles, and why it is never vectorized: it also
sits under a sync exclude of the data source.
packages://<self>/** — brain-core's package folder
The default is read and write, no exec. tools/, skills/, agents/,
rules/, docs/ and assets/ are explicitly read/write; src/** is
read-only.
Source permissions and the safety policy
The declared sources carry their own default permissions: data and
packages read and write without exec, and brain read and write with viewers
read-only on brain://. brain-core also declares one policies entry, a
safety policy (fs-timeout) that bounds every fs_* tool call at 120 seconds.