TreeMap
A free, open-source disk-space visualizer. Squarified treemap, duplicate hunting, disk-full forecasting, and cleanup that only ever moves files to the Trash.
翻译准备中
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证OpenLFCP organization profile, project docs, release notes and backlog.
翻译准备中
取自仓库 README
正在加载完整 README。
查看完整 README ↗Organization-wide GitHub metadata and reusable CI for the OpenLFCP project.
This repository holds shared GitHub configuration only. It contains no protocol specification and no implementation code.
| Repository | Purpose |
|---|---|
spec | Normative specifications, profiles, interoperability vectors, registries, ADR/RFC material |
sdk-ts | Reusable TypeScript LFCP implementation (no Obsidian dependency) |
sdk-rs | Independent Rust LFCP implementation |
server | Application-agnostic reference LFCP server |
obsidian | Obsidian editor adapter and product UI |
examples | Small protocol examples and interoperability demonstrations |
| Document | Purpose |
|---|---|
| docs/BACKLOG-MVP-0.1.md | Authoritative planning source: MVP 0.1 issue numbers, dependencies and acceptance criteria |
| docs/MVP-0.1-PROTOCOL-SCOPE.md | Which parts of LFCP Wire the secure MVP requires, and what is deferred |
| docs/AGENT-OPERATING-GUIDE.md | Source-of-truth hierarchy, repository boundaries and rules for agents and contributors |
| docs/PROJECT-NARRATIVE.md | Project history, vision and architecture narrative |
| docs/ARTIFACTS-INDEX.md | Catalog of every current artifact and the repository it lives in |
| docs/engineering-conventions.md | Branches, commits, validation, labels, versioning and the spec-change process |
CONTRIBUTING.md, SECURITY.md, the issue
forms in .github/ISSUE_TEMPLATE/ and the
pull request template are served by
GitHub to every openlfcp repository that has none of its own, so they are
not copied into the other repositories. Labels
(.github/labels.yml) and
CODEOWNERS are not inherited and are set up per
repository.
The backlog is planning authority only. It does not override the normative
specifications, which live in spec (see spec: README.md for the
source-of-truth table): spec: wire/LFCP-WIRE-01.md,
spec: profiles/SHARED-OBJECTS-PROFILE-01.md,
spec: integration/MARKDOWN-REFS-01.md and the vectors under
spec: test-vectors/. Obsidian architecture lives in
obsidian: docs/OBSIDIAN-ARCHITECTURE-01.md.
./scripts/validate.sh
Requires Ruby (for YAML parsing; preinstalled on GitHub-hosted runners). It checks every YAML file, the labels file and the issue forms.
Apache License 2.0. See LICENSE.