M

Mori cognition VCS command protection

Reviews Mori (cognition VCS) mutations — init, stage, checkout, merge, rebase, commit, reset, stash park/pop/drop, and branch — plus `show -

Reviews Mori (cognition VCS) mutations — init, stage, checkout, merge, rebase, commit, reset, stash park/pop/drop, and branch — plus `show --raw` / `recall --raw` STTP dumps. `mori stash list` and `--help`/`-h` are safe variants of those rules. Other read subcommands are not matched by this source; base Guard policy still applies to the `mori` binary. Community coverage does not certify the upstream tool.

command.mori · v1.0.0 · Other extensions

By Community contributorExternal · opt-inCommand coverage
Try this coverage Install GuardView exact source Mori cognition VCS command protection documentation Claim this coverage
0
Protection rules
11
Permission checks
11
Mapped commands
11

Overview

What this coverage does

Reviews Mori (cognition VCS) mutations — init, stage, checkout, merge, rebase, commit, reset, stash park/pop/drop, and branch — plus `show --raw` / `recall --raw` STTP dumps. `mori stash list` and `--help`/`-h` are safe variants of those rules. Other read subcommands are not matched by this source; base Guard policy still applies to the `mori` binary. Community coverage does not certify the upstream tool.

Key facts

Catalog ID
command.mori
Version
v1.0.0
Kind
Command coverage
Category
Other extensions
Protection rules
11
Permission checks
11
Mapped commands
11
Maintainer
Community contributor(community, provenance recorded)
Source commit
6f36e93
Protection model
External · opt-in
External · opt-in

External coverage. It must be enabled through Guard controls; this page does not activate it.

Stated limits

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

11 operations · 11 reviewed by default These are catalog defaults, not your workspace policy.

11 operations11 reviewed
Default floor

Showing 11 of 11 operations

  • Reviewed Guard intercepts the command for review before it runs.High
    • mori add notes.md
    Mori stage context
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori add`, which stages documents, chats, notes, or STTP into the index.
    Documented safe variants
    Mori add command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.add
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori branch experiment
    Mori branch
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori branch` (list or create). Create mutates refs; list is included because v1 matchers cannot require a branch-name operand after the subcommand alone.
    Documented safe variants
    Mori branch command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.branch-create
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori checkout feature
    Mori branch checkout
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori checkout`, which switches the active cognition branch (optional -b create).
    Documented safe variants
    Mori checkout command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.checkout
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori commit -m 'capture session'
    Mori commit
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori commit`, which compiles staged context into the SurrealKV store.
    Documented safe variants
    Mori commit command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.commit
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori init
    Mori repo init
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori init`, which creates a cognition repo and local SurrealKV store.
    Documented safe variants
    Mori init command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.init
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori merge feature
    Mori branch merge
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori merge`, which brings another branch into the current tip.
    Documented safe variants
    Mori merge command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.merge
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori rebase main
    Mori branch rebase
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori rebase`, which replays the current branch onto another tip.
    Documented safe variants
    Mori rebase command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.rebase
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori reset
    Mori unstage
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori reset`, which unstages context from the index.
    Documented safe variants
    Mori reset command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.reset
  • Reviewed Guard intercepts the command for review before it runs.High
    • mori stash -m 'wip'
    Mori stash mutation
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori stash` parking, pop, and drop. `mori stash list` is a safe variant.
    Documented safe variants
    Mori stash command helpMori stash listskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.stash
  • Reviewed Guard intercepts the command for review before it runs.Medium
    • mori recall 'what shipped?' --raw
    Mori recall raw STTP
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori recall --raw`, which dumps ranked stored STTP payloads.
    Documented safe variants
    Mori recall command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.recall-raw
  • Reviewed Guard intercepts the command for review before it runs.Medium
    • mori show HEAD --raw
    Mori show raw STTP
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `mori show --raw`, which dumps stored STTP for a revision.
    Documented safe variants
    Mori show command helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.mori.permission.show-raw

Tool state mapping

No per-tool overrides are declared. Command defaults above resolve through the workspace Guard policy unless a later policy layer changes them.

Runtime identity

Catalog ID
command.mori
Guard enforcement ID
command.mori
Source path
contributions/extensions/command.mori.json
Contribution digest
sha256…71a453

Action classes

Mori cognition workspace mutationMori stored-context dump

Technical profile

No independent profile published

This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.

FAQ

Frequently asked questions

Reviews Mori (cognition VCS) mutations — init, stage, checkout, merge, rebase, commit, reset, stash park/pop/drop, and branch — plus `show --raw` / `recall --raw` STTP dumps. `mori stash list` and `--help`/`-h` are safe variants of those rules. Other read subcommands are not matched by this source; base Guard policy still applies to the `mori` binary. Community coverage does not certify the upstream tool. The listing declares 11 rules and 11 permission checks. 11 operations · 11 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @zerocodefast, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

11 operations · 11 reviewed by default. Examples: mori add notes.md (reviewed by default); mori branch experiment (reviewed by default); mori checkout feature (reviewed by default); mori commit -m 'capture session' (reviewed by default); mori init (reviewed by default); mori merge feature (reviewed by default); mori rebase main (reviewed by default); mori reset (reviewed by default). The remaining 3 operations are listed in the command mapping table. These are catalog defaults, not your workspace policy.

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.mori in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 11 rules and 11 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.