logicsrc/docs/data-model.md
Anthony Ettinger 68f3151699 Merge master; OpenFleet keeps its name, PR 177's rental descriptor becomes OpenRental
PR 177 shipped a second OpenFleet under the same slug: a published listing of OpenAgent profiles and ipfile swarms with CoinPay rental offers. Anthony ruled that OpenFleet means the human-controlled fleet and the record of who spawned whom, so the rental contract is renamed OpenRental (slug openrental, catalogs family, group noun listing): docs/openrental.md, logicsrc-openrental.schema.json with type logicsrc.openrental and scope kind listing, fixtures/openrental, createOpenRental and OpenRental* types in the SDK, the openrental validator kind. Minor bumps because an export moved: @logicsrc/schemas 0.2.0, @logicsrc/validators 0.2.0, @logicsrc/sdk 0.2.0. The discovery contract test now covers openfleet, openrental and openwall, one per family, and accepts a landing-page link in llms.txt.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01RZV4zJ2pDZLNN3kE5jFCmV
2026-09-13 08:45:33 +00:00

1.3 KiB

Data Model Draft

Core tables:

users
dids
oauth_accounts
connected_accounts
account_permission_grants
account_audit_events
profiles
organizations
organization_members
boards
board_members
posts
threads
comments
tasks
task_bids
task_submissions
agents
agent_capabilities
agent_runs
agent_run_logs
payments
escrows
wallets
reputation_events
files
api_keys
permissions
audit_logs
webhooks
notifications
schemas
schema_versions
plugin_audit_logs
email_message_cache
social_post_cache

Important relationships:

  • User has many DIDs.
  • DID can own agents, boards, tasks, posts, wallets, and API keys.
  • Board has many posts and tasks.
  • Post can link to one task.
  • Task can have one escrow.
  • Task can have many submissions.
  • Agent can have many runs.
  • Agent run belongs to one task.
  • OpenRental groups OpenAgent profile references and/or OpenSwarm file-key references, with listing metadata and CoinPay rental offers scoped to the listing or named members.
  • Reputation events belong to DIDs.
  • API keys belong to users, agents, or service accounts.
  • Permissions are scoped to resources.
  • LogicSRC-compatible objects record their schema version.
  • Connected social and email accounts reference credentials through a broker and use account permission grants plus account audit events for agent-safe delegation.