Cross-platform source/path sync collaboration layer for humans and agents, built on Apache OpenDAL.

Section's active product model is:

• source/path is the primary mental model
• a source can bind to a local directory
• files and directories sync into that local tree
• public state stays simple: ready / syncing / conflict / error
• sectiond is the source/path sync core
• CLI / API / GUI are the control plane
• execution is outside the current project scope

• docs/PRODUCT.md
• docs/AGENTFS_REQUIREMENTS.md
• docs/AGENTFS_DESIGN_PROPOSAL.md
• docs/AGENTFS_MVP_CONTRACT.md
• docs/AGENTFS_TEST_PLAN.md
• docs/AGENTFS_DEVELOPMENT_READINESS.md
• docs/issues/004-agentfs-review-triage.md
• docs/ARCHITECTURE.md
• docs/SYNC_MODEL.md
• docs/SECTIOND.md
• docs/PLAN.md
• docs/QUICKSTART.md
• docs/USER_MANUAL.md
• docs/PROMO.md
• docs/release/README.md
• docs/distribution/homebrew/README.md
• docs/distribution/npm/README.md

The current repo already includes:

• source registry persisted in the provider store
• source to local-root binding
• .section/root.json local discovery markers
• source/path sync state persistence
• source/path event persistence
• bidirectional source sync with stale-overwrite conflict detection
• local-path-first control-plane commands:
  • section source bind
  • section source unbind
  • section source sync
  • section path inspect
  • section path compare
  • section path resolve
  • section watch

The active route in this repo is centered on:

• section-core
• section-provider
• section-cli
• sectiond

Any provider supported by OpenDAL can be used. Common ones:

See OpenDAL services for the full list.

cargo check -p section-core -p section-provider -p section-cli -p sectiond
cargo test -p section-core -p section-provider -p sectiond
cargo test -p section-cli
RUST_LOG=debug section source list

Apache-2.0