wave-plan

Kind: feature

Decide which beads may run at once from the code-level independence of their node scopes, and state the media a wave shares regardless

Source: src/beadloom/application/waves/

Public symbols

• BeadRecord
• BeadScope
• Conflict
• Declaration
• ExtrasChoice
• FocusDocument
• GraphFile
• GraphInput
• LockInvocation
• LockSite
• MediumCheck
• OverrideOutcome
• Population
• RoomBuild
• RoomEnvironment
• RoomRequest
• RunningConflict
• RunningWork
• ScopeAgreement
• SharedMedium
• TrackerBead
• TrackerCensus
• UnguardedAxis
• Wave
• WaveConfigError
• WaveEnvironment
• WaveOverride
• WavePlan
• WorkItemAxes
• bead_ids
• beads_under
• build_environment
• build_room
• check_media
• compare_declarations
• compose_declaration
• conflict_between
• conflicts_among
• conflicts_with_running
• declared_refs
• defect_detail
• derivation_findings
• derive_population
• extras_a_room_installs
• finding_for
• load_overrides
• lock_sites
• parse_declaration
• plan_waves
• population_findings
• population_lines
• ready_under
• remedy_for
• resolve_scope
• resolve_scopes
• room_for
• room_invocation
• room_owner
• room_path
• room_python
• room_request
• running_findings
• running_lines
• running_population
• running_summary
• site_packages
• sorted_pair
• title_id_mismatches
• title_references
• unguarded_axes

Relationships

• part_of: application
• depends_on: active-table, beadloom, graph-layout, repository, rule-engine, verdict-room
• Used by: bd-seam, cli-commands, declared-scope, gate-ownership, guard-probes, mcp-server, review-brief

Documentation

• domains/application/features/wave-plan/SPEC.md

Diagram