Buildalphaknowledge

Knowledge catalog

What does the network's own knowledge catalog say?

Source and guide ↗
flop knowledge --help

Follow a concept to its declared sources. Read what the catalog claims, then inspect the source limits.

Recorded observationPublic MCP source ↗Download recording ↓
Received concepts155
Resolved declared edges340
Unresolved references181
Catalog confidence is a claim.

provenance unavailable: repo sources are not mounted next to the catalog

Lifecycle and confidence below are the service's labels. This page does not verify source hashes or deployed behavior.

Explore the catalog

Start with a concept.

Search the full manifest. Select a node to move through its declared relationships.

155 matching concepts
1 / 13

Directed neighborhood

FLOP Knowledge Catalog Overview

Knowledge Catalog
overview exposes agent-packoverview exposes public-discoveryoverview exposes internal-skillsoverview exposes repo-domainsoverview exposes software-componentsoverview exposes docs-navigationoverview exposes source-gapsoverview exposes mcp-toolsrepo-domains depends_on overviewdocs-navigation depends_on overview◎FLOP Knowledge Catalog O...FLOP Knowledge Catalog Overview↗FLOP Agent Context PackFLOP Agent Context Pack↗FLOP Public Agent DiscoveryFLOP Public Agent Discovery↗FLOP Internal Agent Skil...FLOP Internal Agent Skill Catalog↗FLOP Repo Domain CatalogFLOP Repo Domain Catalog↗FLOP Software Component ...FLOP Software Component Catalog↗FLOP Documentation Navig...FLOP Documentation Navigation↗FLOP Source Gap CatalogFLOP Source Gap Catalog↗FLOP MCP Tool CatalogFLOP MCP Tool Catalog

8 of 14 linked concepts shown. Arrows follow declared direction. Spacing has no semantic weight.

FLOP Knowledge Catalog Overview

Review bundle for agent-facing FLOP context, generated from code and docs.

Claimed confidence
source-backed
Lifecycle label
generated

overview.md

Declared resource ↗
flop knowledge get 'overview' --live --json

Reading guide

From catalog label to source limit

The line tracks your place in this explanation.

Read the declaration

Concepts provide a title, lifecycle and confidence label. Those labels come from the catalog.

Follow a typed arrow

Edges retain the service's relationship name and direction. Unresolved references stay visible rather than becoming invented nodes.

Inspect the source

Open the raw response. Missing provenance, line ranges and hashes remain missing. Reading progress is not verification progress.

Requirement explainer

Keep the citation attached.

The bundled example is R9.5. Other keys require the live CLI.

R9.5: Validator pool split

Spec claim
normative
Implementation claim
DIVERGENT: the runtime splits by `total_stake` with a 1.1× committee premium (`FINALITY_COMMITTEE_PREMIUM_WEIGHT_PPM`, deprecated)
Evidence claim
unknown
- **R9.5 - Validator pool split.** The block-reward validator 10% pool
  ([`validator_share_ppt`](#param-validator_share_ppt) = 100 ppt) **MUST NOT** be increased by an
  emission surcharge or a second mint. (The separate 15% inference-fee validator share is an extrinsic
  settlement fee leg, not an emission or dilution of block rewards; see [Appendix D](#appendix-d--fee--revenue-map)).
  It **MUST** be split in equal shares among the active seats, with no stake weight and no committee
  premium, and with integer dust assigned deterministically so payouts sum exactly to the pool. A seat
  whose SLA window fails forfeits that window's share (R15.5c; the forfeiture sink is E.59). The
  validator inference-fee leg (R12.1a) **MUST** use the same equal per-seat split. This holds unchanged under
  the four-way split: the agent and staker legs are carved **out of the miner residual**
  ([`miner_share_ppt`](#param-miner_share_ppt) 900 → 750 ppt), never added on top, so
  `validator_share_ppt` stays at 100 ppt.

Cited source paths

  • flop-labs/flop-core/whitepaper/yellowpaper.md#91-requirements

    Line range: not supplied. Hash: not supplied.

Concepts sharing an exact cited source path

These links match paths. They do not establish implementation or independent corroboration.

Agent context pack

Discovery is not installation.

The catalog describes a pack. The recorded pack endpoints report a missing pack. Both answers are retained.

Unavailable at read

Pack manifest

flop_agent_pack_manifest

agent pack missing; set FLOP_AGENT_PACK_DIR or checkout knowledge/agent-pack

Unavailable at read

Skill text

flop_agent_skill_get

agent pack missing; set FLOP_AGENT_PACK_DIR or checkout knowledge/agent-pack

Unavailable at read

Install guidance

flop_agent_pack_install

agent pack missing; set FLOP_AGENT_PACK_DIR or checkout knowledge/agent-pack

Negative discovery probe

Agent card

flop_get_agent_card

no agent registered for id 0x0000000000000000000000000000000000000000000000000000000000000000

The all-zero card ID is a negative probe, not an observed registered agent. No conclusion about other agent IDs follows from it. Returned commands and URLs are never executed.

What this does not verify

No runtime state, deployed code, agent identity, source hash, inference result or chain finality is verified. Status text is quoted from the service. Missing source provenance remains a limit on every catalog claim.