Dontopedia

Plan Marking

From Dontopedia, the open, paraconsistent wiki. (Last updated 2026-06-07.)

Plan Marking has 7 facts recorded in Dontopedia across 3 references, with 1 live disagreement.

7 facts·5 predicates·3 sources·1 in dispute

Mostly:rdf:type(3), results in(1), action description(1)

Maturity scale raw canonical shape-checked rule-derived certified

Inbound mentions (5)

Other subjects in dontopedia point AT this entity as a value. These are inverse relationships — e.g. "X motherOf this subject" — and answer questions the forward facts can't. Grouped by predicate.

enablesEnables(2)

hasPurposeHas Purpose(2)

resultsInResults in(1)

Other facts (7)

The long tail: predicates that appear too rarely to warrant their own section. Filter or scroll to find a specific one. Each row links to its source.

7 facts
PredicateValueRef
Rdf:typeGoal[1]
Rdf:typeData Entry Action[2]
Rdf:typeAction[3]
Results inCritical Plan Identification[1]
Action DescriptionMark Plans as Critical[3]
Requires Selection ofCritical Status[3]
Performed inPriority Column[3]

Timeline

Timeline axis is valid_time — when each source says the fact was true in the world, not when Dontopedia learned about it. Retracted rows are kept for provenance; coloured stripes indicate the context kind.

typebeam/52299184-8ea8-49f9-8741-5c12c05726df
ex:Goal
resultsInbeam/52299184-8ea8-49f9-8741-5c12c05726df
ex:critical-plan-identification
typebeam/3d099c65-1414-416f-8d06-94009d7e27d1
ex:DataEntryAction
typebeam/6bc8ee07-d062-4399-8317-5500b38a3b1e
ex:Action
actionDescriptionbeam/6bc8ee07-d062-4399-8317-5500b38a3b1e
Mark Plans as Critical
requiresSelectionOfbeam/6bc8ee07-d062-4399-8317-5500b38a3b1e
ex:critical-status
performedInbeam/6bc8ee07-d062-4399-8317-5500b38a3b1e
ex:priority-column

References (3)

3 references
  1. ctx:claims/beam/52299184-8ea8-49f9-8741-5c12c05726df
    • full textbeam-chunk
      text/plain1 KBdoc:beam/52299184-8ea8-49f9-8741-5c12c05726df
      Show excerpt
      - Checks if a user can access a specific plan based on their role and the plan's criticality. ### Conclusion By defining clear roles and implementing role-based access control, you can effectively manage access to your project plans an
  2. ctx:claims/beam/3d099c65-1414-416f-8d06-94009d7e27d1
    • full textbeam-chunk
      text/plain1 KBdoc:beam/3d099c65-1414-416f-8d06-94009d7e27d1
      Show excerpt
      - For each plan you want to mark as critical, add the "Critical" tag in the "Tags" column. ### Example Implementation in Monday.com Here's a step-by-step example using a status column: 1. **Navigate to Your Board:** - Open the boar
  3. ctx:claims/beam/6bc8ee07-d062-4399-8317-5500b38a3b1e
    • full textbeam-chunk
      text/plain1 KBdoc:beam/6bc8ee07-d062-4399-8317-5500b38a3b1e
      Show excerpt
      - Can view and edit all critical plans. 2. **Team Lead (TL)** - Access to specific boards and items related to their teams/modules. - Can view and edit a subset of critical plans (4%). 3. **Developer (Dev)** - Access to specif

See also

Keep researching

Missing something or suspicious of what's here? Kick off a research session — a Claude agent will investigate, cite its sources, and file new facts into a dedicated context you can review before accepting into the shared view.