Concept Boundary Definition

Template Overview

Intellectual confusion usually stems from fuzzy vocabulary. When terms like ‘privacy’, ‘security’, ‘anonymity’, and ‘confidentiality’ are conflated, system architecture suffers. The Concept Boundary Definition template applies rigorous philosophical and analytical discipline to terms in your knowledge vault. It establishes necessary and sufficient conditions, documents what the concept explicitly is NOT, maps neighboring semantic neighbors, and analyzes borderline edge cases.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Concept Boundary: [Term / Concept Name]"
date_defined: [YYYY-MM-DD]
domain_taxonomy: "[Epistemology / Systems Architecture / Cryptography / Ethics]"
canonical_term: "[Exact Terminology]"
semantic_status: "[Settled / Contested / Emerging]"
tags: [ontology, definitions, epistemology, pkm, conceptual-clarity, mental-models]
---

# Concept Boundary Definition — [Canonical Term]

## 1. The Core Definition & Formal Essence
- **Term:** `[e.g., Data Sovereignty]`
- **The Formal Definition:** The legal and architectural state wherein an individual or organization possesses exclusive, unchallengeable control over the storage, processing, and transmission of their digital information without reliance on unvetted intermediaries.
- **Genus & Differentia:** It is a form of *computational self-determination* (Genus) distinguished by *complete physical and cryptographic independence from third-party cloud infrastructure* (Differentia).

## 2. What This Concept Is NOT (Negative Boundaries)
*Clarify boundaries by distinguishing the term from frequent confusions:*
- **It is NOT merely 'Data Privacy':** Privacy is the expectation that personal data will not be viewed; sovereignty is the mathematical impossibility of unauthorized access through physical ownership.
- **It is NOT 'Cloud Encryption at Rest':** If a cloud provider holds master encryption keys or executes decryption routines on remote servers, sovereignty does not exist.
- **It is NOT 'Data Portability':** Being able to export a JSON file from a proprietary SaaS platform does not constitute sovereignty if ongoing usage requires the platform.

## 3. Contrast Matrix with Semantic Neighbors
| Term | Core Meaning | How It Differs from [Target Concept] | Overlap Area |
|---|---|---|---|
| **Confidentiality** | Agreement not to disclose data | Relies on trust and legal contracts; sovereignty relies on architecture | Both seek to shield information |
| **Security** | Resistance to attack | A cloud service can be highly secure yet violate sovereignty | High security is necessary but insufficient for sovereignty |
| **Anonymity** | Shielding identity | You can have total sovereignty over fully identified personal notes | Anonymity can enhance sovereign systems |

## 4. Borderline Edge Cases & Stress Tests
- **Edge Case 1: Client-Side Encrypted Cloud Backups:**
  - *Dilemma:* If notes are encrypted with zero-knowledge AES-256 keys on your Mac before syncing to an S3 bucket, is that sovereign?
  - *Verdict:* Conditionally sovereign. The storage medium is non-sovereign, but cryptographic control remains sovereign so long as keys never leave local silicon.
- **Edge Case 2: On-Device AI Downloading Model Weights:**
  - *Verdict:* Sovereign. Downloading read-only model weights once over HTTPS is equivalent to buying a physical book; no user data leaves the machine.

## 5. Vault Ontology Links
- Parent Concept: `[[knowledge-graph-ontology-spec]]`
- Application Note: `[[atomic-permanent-note]]` on local-first computing
- Real-World Implementation: `[[architecture-decision-record]]`

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Concept Boundary: Local-First Software"
date_defined: 2026-10-09
domain_taxonomy: "Systems Architecture"
canonical_term: "Local-First Software"
semantic_status: "Settled"
tags: [ontology, definitions, epistemology, pkm, conceptual-clarity, mental-models]
---

# Concept Boundary Definition — Local-First Software

## 1. Formal Definition
Software where primary data storage and compute execution happen on local hardware, functioning with 100% feature parity when internet connectivity is completely severed.

## 2. What It Is NOT
- It is NOT 'Offline Mode' (a degraded temporary cache that eventually requires cloud reconnection).
- It is NOT purely open-source (proprietary software can be local-first; open-source web SaaS is not local-first).

## 3. Core Test
If you sever Wi-Fi, throw away the internet router, and continue working for 5 years without a server connection, does the software still function fully? If yes, it is local-first.

When to Use and When to Avoid

When to Use

• Use when defining foundational architectural, philosophical, or domain terms in your personal vault.
• Use to prevent team members or co-authors from using critical vocabulary ambiguously.
• Use during doctoral research to define operational terms before empirical investigation.

When to Avoid

• Avoid using for everyday colloquial terms with obvious everyday meanings.
• Avoid using for ephemeral project task descriptions.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the concept boundary definition:
1. Examine the genus-differentia definition for logical circularity or ambiguity.
2. Formulate two difficult edge cases designed to test the boundary limits of the definition.
3. Suggest a semantic neighbor term that was omitted and provide a contrast comparison.
Output in structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.