npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cognitor/protocol

v1.0.0

Published

> **口号:让逻辑裂隙无所遁形** > **愿景:人类认知的工业级脚手架**

Readme

@cognitor/protocol | 康构特·认知协议

口号:让逻辑裂隙无所遁形 愿景:人类认知的工业级脚手架

1. 项目动机 (Motivation)

在构建「康构特·重构理性」的过程中,我们发现认知的复杂性来自于“模糊”与“谬误”。为了消除这些裂隙,我们需要一个架构无关 (Architecture Agnostic) 的底层契约。

本协议层的核心动机在于:

  • 解耦核心逻辑与执行模式:无论是单机 DAG 流转,还是万亿级数据的分布式对撞,其底层语义必须统一。
  • 空间隔离的实质化:从协议层注入 spaceIdboundary,确保认知空间的安全性与主权。
  • 工业级溯源:每一条逻辑偏移(Gap)都必须拥有不可篡改的 Lineage(溯源链)。

2. 设计哲学 (Design Philosophy)

  • Sharp (锋利):接口定义直击逻辑本质,禁止过度包装。
  • Profound (深刻):优先考虑概念完整性(Concept First),区分“现实”、“代码”与“架空”本体。
  • Truthful (诚实):协议本身不持有立场,只负责定义“如何描述真相及其偏移”。

3. 分层架构 (L1-L3)

  • L1 - 算子层 (Operator):定义 CognitiveNode,解决具体的逻辑处理单元。
  • L2 - 存储层 (Storage):定义数据的持久化与检索契约(由 Core 扩展实现)。
  • L3 - 执行策略层 (Strategy):定义架构的运行模式,实现从 MVP 到大规模集群的无缝切换。

4. 协作规范 (Standards)

  1. 禁止逻辑实现:本包仅允许存在接口 (interface)、类型 (type) 和枚举 (enum)。
  2. 不可变性:所有执行上下文 (ExecutionContext) 字段必须设为 readonly
  3. 零依赖:禁止依赖 core 或其他业务包,保持协议的最底层纯净度。