docs(post-mvp): Lobby DNA requirements and architecture design#87
Merged
Conversation
Introduces the multi-network federation documentation layer: - documentation/requirements/post-mvp/lobby-dna.md Formal requirements (REQ-LOBBY-*, REQ-GROUP-*, REQ-NDO-EXT-*) for the Lobby DNA, Group DNA, and NDO DNA extensions. Covers three-DHT model, two link tiers (soft/hard), governance layers, Flowsta and Unyt integration hooks, and dual deployment (standalone + Moss applet). - documentation/specifications/post-mvp/lobby-architecture.md Full architecture design: C4 diagrams, entry types, link types, coordinator APIs, validation rules, sequence diagrams for the Incorporation and Process pipelines, Svelte 5 UI component map, Moss WeApplet integration contract, and 7 ADRs. - documentation/DOCUMENTATION_INDEX.md Added both new documents to the Core Documentation and Architecture & Roadmap tables. - documentation/requirements/requirements.md §2.3 Added Lobby DNA row to the post-MVP capability integrations table alongside Unyt and Flowsta. Status: Post-MVP — specified and documented; not yet implemented in WASM. Based on: requirements discovery session + Moss/Weave ecosystem research (2026-04-14).
Aligns field names, entry semantics, and type names with the
ValueFlows 1.0 specification to eliminate the translation layer
at Unyt/RAVE integration points.
Changes:
WorkLog (Group DNA):
author -> provider (VF: provider)
description -> note (VF: note)
effort_hours -> effort_quantity (VF: effortQuantity)
process_context -> input_of (VF: inputOf; string for MVP,
ActionHash post-MVP when Process entries exist)
logged_at -> has_point_in_time (VF: hasPointInTime)
+ action: VfAction field added (VF: action)
SoftLink (Group DNA):
link_purpose: SoftLinkPurpose enum removed
-> planned_action: VfAction (Combine | Use | Cite)
commitment_hash -> fulfills (VF: fulfills)
Contribution (NDO DNA extensions):
contributor -> provider (VF: provider)
description -> note (VF: note)
effort_hours -> effort_quantity (VF: effortQuantity)
process_context -> input_of (VF: inputOf)
contributed_at -> has_point_in_time (VF: hasPointInTime)
+ action: VfAction field added (VF: action)
+ fulfills field renamed (VF: fulfills)
SmartAgreement -> Agreement (VF: vf:Agreement)
accountable_agents -> primary_accountable (VF: primaryAccountable)
rules: Vec<BenefitRule> -> clauses: Vec<BenefitClause> (NDO extension)
BenefitRule -> BenefitClause
beneficiary -> receiver (VF: receiver)
conditions -> note (VF: note)
Link types:
NdoToSmartAgreement -> NdoToAgreement
SmartAgreementUpdates -> AgreementUpdates
AgentToContributions: note VF provider semantics
ContributionToEvent: note VF fulfills semantics
Coordinator files:
smart_agreement.rs -> agreement.rs
All pipeline diagrams, UI component names, and ADRs updated.
Thingiverse is a proprietary platform (Makerbot/Stratasys), not an OVN. Open Source Ecology is a genuine open value network.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Adds two conceptual sections missing from the original design docs. lobby-architecture.md §2 (new opening subsections): 'Agent identity layers' — LobbyAgentProfile vs Person table, pubkey flow diagram (Lobby -> Group -> NDO), ndo_pubkey_map as MVP bridge, Flowsta post-MVP note, implementer implication. 'Groups vs organization-NDOs' — comparison table (identity, custody, reputation, governance, permanence), worked Sensorica example, key architectural rule (NDO contribution != group membership), post-MVP AgentContext gap callout. lobby-dna.md §3 (new normative subsections after 'Two link tiers'): 'Agent identity layers' — three-bullet normative summary pointing to arch spec for diagram. 'Groups vs organization-NDOs' — four-bullet normative constraints pointing to arch spec for comparative table.
- REQ-GROUP-12: add VfAction mapping (Incorporation→Combine, Use→Use, Monitoring→Cite) - lobby-dna.md §6.3: clarify entry type is Agreement (VF-aligned), add intro note - REQ-NDO-EXT-12: fix 'a Agreement' → 'an Agreement' - ndo_prima_materia.md: add lobby-dna.md to Relates to header + §11.7 Lobby DNA stub
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…plan - IMPLEMENTATION_STATUS: add Lobby DNA + NDO DNA extensions rows to post-MVP table - implementation_plan §1.1: add lobby-dna.md to requirements map - implementation_plan §4: mention Lobby DNA in Extended post-MVP track - implementation_plan §12.6: full Lobby DNA design track with ordered checklists and dependencies
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
…mentation_plan - lobby-dna.md §6.1: add design note explaining NdoHardLink.to_ndo_dna_hash changes in value (not shape) between Stage 2 (shared cell) and Stage 3 (per-NDO cloned cells); same struct, no breaking change at migration - implementation_plan.md §12.6: inline the Stage 2/Stage 3 deployment note in the NdoHardLink checklist item
…bby-architecture - NdoDescriptor §4.4: remove successor_ndo_hash and hibernation_origin from create validation — these fields do not exist on NdoDescriptor (they are NondominiumIdentity-specific); leftover from copy-paste - Agreement §6.4: add AccountableAgent role check to create Agreement (REQ-NDO-EXT-12); add update Agreement rules (role check, version increment, immutable ndo_identity_hash); add delete Agreement: INVALID (versioned history preserved via supersession)
This was referenced Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
Document the Lobby DNA multi-network federation layer — the architectural foundation for letting Nondominium agents discover, coordinate around, and connect to multiple independent NDO networks (each its own DHT).
This PR adds the requirements specification and full architecture design produced during a dedicated design session on 2026-04-14, based on:
Changes
documentation/requirements/post-mvp/lobby-dna.mddocumentation/specifications/post-mvp/lobby-architecture.mddocumentation/DOCUMENTATION_INDEX.mddocumentation/requirements/requirements.mdKey Decisions
Status
Post-MVP — specified and documented; not yet implemented in WASM. This PR is a planning artifact, not an implementation. Implementation will follow in a separate feature branch.
Related
documentation/requirements/post-mvp/flowsta-integration.md(identity integration)documentation/requirements/post-mvp/unyt-integration.md(economic settlement)documentation/requirements/post-mvp/many-to-many-flows.md(multi-party consent)documentation/requirements/ndo_prima_materia.md§6, §8, §11 (normative NDO requirements)How to review
Read the two new files in order:
requirements/post-mvp/lobby-dna.md— what must be built and whyspecifications/post-mvp/lobby-architecture.md— how it is designed