Page types
Distinguish artifact, creator and communication-identity records.
Clawdbase uses separate Page types because the evidence and decision meaning differ.
| Page | What it evaluates | Typical source |
|---|---|---|
| Agent | An executable or autonomous software artifact | GitHub repository or canonical Agent record |
| Skill | An installable capability or extension | GitHub repository or package evidence |
| Creator | The person or organization behind artifacts | GitHub identity and repository relationships |
| X account | A communication identity | X OAuth identity |
| Telegram | An account, channel or bot identity | Telegram-native authentication/control |
Scores do not transfer across types. A trusted communication account is contextual evidence, not proof that associated code is secure.
System facts and presentation
Canonical identifiers, verification timestamps, score fields and lineage are system-managed. On plans that support owner-managed presentation, owners may edit descriptive fields without changing the authoritative facts.
Agent
An Agent is an executable or autonomous software artifact. Its Page emphasizes the repository or canonical artifact identity, Agent Trust and Confidence, Creator context and optional lineage. The developer operation is agent_score; use agent_skill_lineage when upstream relationships are part of the decision.
Skill
A Skill is an installable capability, integration or extension. Its Page supports an installation decision and keeps its score separate from the Creator who authored it. Similar repository names do not make two Skills the same canonical object.
Creator
A Creator is the person or organization behind one or more artifacts. GitHub is the primary authority for this developer identity. A Creator score provides origin context; it does not replace Agent or Skill evidence.
X account
An X account is a communication identity anchored by the immutable X user ID returned through OAuth. The current handle is a mutable display and routing value. Its score describes the account, not code mentioned by the account.
Telegram account
A Telegram Page may represent an account, channel or bot. Each kind needs the matching Telegram-native proof. Authenticating a personal account does not automatically prove administration of every channel or control of every bot.
Choosing a type during GitHub registration
After GitHub OAuth, the authenticated user selects from assets the backend confirms they can control. A user identity produces a Creator Page. An authorized repository may be registered as an Agent or Skill according to the selected artifact kind. The immutable repository ID anchors matching even if the repository is renamed.
Cross-type relationships
Relationships provide context without collapsing records. One Creator can own several Agents and Skills; an Agent can be discussed by X or Telegram identities; and lineage can connect an artifact to upstream artifacts. Each Page keeps its own score, verification state and timestamp.