What Artifacts MEAN¶
Layer 2 defines extrinsic dimensions—calculated properties that interpret what artifacts mean in specific contexts. Unlike Layer 1 properties stored in frontmatter, Layer 2 dimensions are computed on-demand in dashboards and queries.
The Key Insight¶
Same artifact, different meanings:
A research note with refinement: 0.65 might be:
Ready for personal reference
Usable for internal lab sharing
Insufficient for external publication
The intrinsic property (refinement: 0.65) doesn’t change. The extrinsic dimension (usefulness) depends on context (who’s the audience, what’s the quality gate).
This separation enables context-aware knowledge management without duplicate metadata.
16 Extrinsic Dimensions¶
Dimensions are organized into 5 categories:
| Category | Dimensions | Purpose |
|---|---|---|
| State | health, usefulness, compliance_fit, trust_level, freshness, coverage_fit | Current quality and fitness |
| Trajectory | drift, health_trend, adoption | Change over time |
| Network | network_position, propagation_risk | Role in knowledge graph |
| Workflow | stage, blocking_status | Process position |
| Priority | attention_priority, retention_value, effort_to_improve | Decision support |
State Dimensions¶
Health¶
Purpose: Overall artifact quality
Calculation: Based on refinement score and stubs count
| Value | Refinement Range | Stubs | Interpretation |
|---|---|---|---|
| excellent | 0.85 - 1.00 | 0 | Publication-ready, evergreen |
| good | 0.70 - 0.84 | 0-1 | High quality, minor gaps |
| fair | 0.50 - 0.69 | 0-3 | Usable, needs improvement |
| poor | 0.30 - 0.49 | any | Developing, significant work needed |
| critical | 0.00 - 0.29 | any | Initial capture, rough notes |
Example query:
SELECT title, refinement, stubs_count
FROM notes
WHERE health IN ('poor', 'critical')
ORDER BY refinement ASCUsefulness¶
Purpose: Fitness for intended audience
Calculation: refinement vs audience-specific quality gate
| Audience | Quality Gate | Interpretation |
|---|---|---|
| personal | 0.30+ | Ready for personal use |
| internal | 0.60+ | Usable for team sharing |
| public | 0.80+ | Sufficient for external sharing |
| published | 0.90+ | Publication-ready |
Usefulness values:
| Value | Meaning | Example |
|---|---|---|
| ready | Exceeds quality gate by 0.10+ | refinement: 0.75 for audience: internal (gate: 0.60) |
| usable | Meets quality gate | refinement: 0.62 for audience: internal |
| developing | Below gate by < 0.20 | refinement: 0.45 for audience: internal |
| insufficient | Below gate by 0.20+ | refinement: 0.30 for audience: internal |
Example implementation:
def calculate_usefulness(refinement, audience):
gates = {
'personal': 0.30,
'internal': 0.60,
'public': 0.80,
'published': 0.90
}
gate = gates[audience]
delta = refinement - gate
if delta >= 0.10:
return 'ready'
elif delta >= 0:
return 'usable'
elif delta >= -0.20:
return 'developing'
else:
return 'insufficient'Compliance Fit¶
Purpose: Alignment with standards, policies, or requirements
Calculation: Based on refinement, stubs, required metadata presence
| Value | Criteria | Use Case |
|---|---|---|
| compliant | Meets all requirements | Regulatory docs, publication requirements |
| partial | Meets core requirements | Internal policies, team standards |
| non-compliant | Missing requirements | Needs remediation |
Example: Publication Requirements
| Requirement | Check | Status |
|---|---|---|
| Refinement ≥ 0.90 | ✅ 0.92 | Pass |
| No stubs | ✅ 0 stubs | Pass |
| Has DOI | ❌ Missing | Fail |
| Peer reviewed | ✅ Yes | Pass |
| Result | partial |
Trajectory Dimensions¶
Drift¶
Purpose: How much has the artifact’s alignment with its original purpose decayed?
Calculation: Based on time since creation, edit frequency, refinement changes
| Value | Time Since Edit | Refinement Trend | Interpretation |
|---|---|---|---|
| none | < 30 days | stable/improving | Actively maintained |
| minimal | 30-90 days | stable | Recently reviewed |
| moderate | 90-180 days | stable | Aging, review soon |
| significant | 180-365 days | declining | Needs attention |
| severe | > 365 days | declining | Likely outdated |
Example query:
SELECT title, days_since_edit, refinement
FROM notes
WHERE drift IN ('significant', 'severe')
AND form = 'evergreen'
ORDER BY days_since_edit DESCHealth Trend¶
Purpose: Is quality improving, stable, or declining?
Calculation: Compare recent refinement changes
| Value | Refinement Δ (30 days) | Interpretation |
|---|---|---|
| improving | +0.10 or more | Active improvement |
| stable | -0.05 to +0.10 | Consistent quality |
| declining | -0.05 to -0.20 | Quality decay |
| deteriorating | -0.20 or worse | Critical decline |
Example dashboard:
| Note | Refinement (30d ago) | Refinement (now) | Δ | Trend |
|---|---|---|---|---|
| Literature Review | 0.75 | 0.85 | +0.10 | improving ✅ |
| Methodology | 0.90 | 0.88 | -0.02 | stable ➡️ |
| Experiment Log | 0.65 | 0.50 | -0.15 | declining ⚠️ |
| Old Notes | 0.70 | 0.40 | -0.30 | deteriorating 🚨 |
Network Dimensions¶
Network Position¶
Purpose: What role does this artifact play in the knowledge graph?
Calculation: Based on incoming/outgoing links, citation count
| Value | Links In | Links Out | Interpretation |
|---|---|---|---|
| hub | High (10+) | High (10+) | Central knowledge node |
| connector | Medium (5-10) | Medium (5-10) | Bridges concepts |
| peripheral | Low (1-5) | Low (1-5) | Specialized, narrow scope |
| isolated | 0-1 | 0-1 | Disconnected from graph |
Example network analysis:
| Note Type | Avg Links In | Avg Links Out | Position |
|---|---|---|---|
| Concept Maps | 15 | 12 | hub |
| Literature Reviews | 8 | 6 | connector |
| Experiment Logs | 3 | 2 | peripheral |
| Quick Notes | 0 | 0 | isolated |
Propagation Risk¶
Purpose: If this artifact has errors, how many others are affected?
Calculation: Network position + health + outgoing links
| Value | Criteria | Impact |
|---|---|---|
| critical | Hub with poor health | Errors spread widely |
| high | Connector with fair health | Moderate propagation |
| moderate | Peripheral, any health | Limited spread |
| low | Isolated, any health | Contained impact |
| negligible | Excellent health, any position | No risk |
Example risk matrix:
| Hub | Connector | Peripheral | Isolated | |
|---|---|---|---|---|
| excellent | low | negligible | negligible | negligible |
| good | moderate | low | negligible | negligible |
| fair | high | moderate | low | negligible |
| poor | critical 🚨 | high | moderate | low |
| critical | critical 🚨 | critical | high | moderate |
Workflow Dimensions¶
Stage¶
Purpose: Where is this artifact in its lifecycle?
Calculation: Based on form, refinement, stubs, workflow context
Standard workflow stages:
| Stage | Typical Criteria | Next Actions |
|---|---|---|
| capture | form: transient, low refinement | Decide: develop or discard |
| develop | form: developing, moderate refinement | Iterate, refine, connect |
| review | refinement ≥ 0.70, some stubs | Peer review, validate |
| polish | refinement ≥ 0.80, few stubs | Final edits, formatting |
| published | refinement ≥ 0.90, no stubs | Maintain, update as needed |
| archived | form: archived | Preserve, no active work |
Example workflow dashboard:
| Stage | Count | Avg Refinement | Actions |
|---|---|---|---|
| capture | 45 | 0.35 | Triage weekly |
| develop | 23 | 0.58 | Active work |
| review | 8 | 0.75 | Schedule reviews |
| polish | 3 | 0.85 | Final pass |
| published | 67 | 0.92 | Maintenance mode |
| archived | 120 | 0.65 | Preserve only |
Blocking Status¶
Purpose: Is progress on this artifact blocked?
Calculation: Based on stubs content, dependency tags, external factors
| Value | Criteria | Example |
|---|---|---|
| blocked | Can’t proceed | “Awaiting IRB approval”, “Need dataset access” |
| at_risk | Potential blockers | “Co-author hasn’t responded in 2 weeks” |
| clear | No impediments | Normal progress |
Implementation example:
# Blocked artifact
---
refinement: 0.60
stubs:
- "BLOCKED: Awaiting ethics approval"
- "Need institutional access to dataset"
blocking_status: blocked # calculated
---Priority Dimensions¶
Attention Priority¶
Purpose: What should I work on next?
Calculation: Synthesis of health, usefulness, drift, network position, blocking status
| Value | Criteria | Recommendation |
|---|---|---|
| critical | Poor health + hub position + high drift | Work on this immediately |
| high | Below quality gate + approaching deadline | Schedule this week |
| medium | Moderate health + some drift | Plan for this month |
| low | Good health + stable | Maintain as needed |
| defer | Excellent health + isolated | No action needed |
Example priority calculation:
def calculate_attention_priority(note):
score = 0
# Health component
if note.health in ['critical', 'poor']:
score += 3
elif note.health == 'fair':
score += 2
# Network component
if note.network_position == 'hub':
score += 2
elif note.network_position == 'connector':
score += 1
# Drift component
if note.drift in ['significant', 'severe']:
score += 2
elif note.drift == 'moderate':
score += 1
# Usefulness component
if note.usefulness == 'insufficient':
score += 2
elif note.usefulness == 'developing':
score += 1
# Blocking component
if note.blocking_status == 'blocked':
score += 1
# Map score to priority
if score >= 7:
return 'critical'
elif score >= 5:
return 'high'
elif score >= 3:
return 'medium'
elif score >= 1:
return 'low'
else:
return 'defer'Priority dashboard example:
| Note | Health | Position | Drift | Usefulness | Score | Priority |
|---|---|---|---|---|---|---|
| Core Methodology | poor | hub | significant | insufficient | 9 | 🚨 critical |
| Literature Survey | fair | connector | moderate | developing | 6 | ⚠️ high |
| Experiment Log | good | peripheral | minimal | ready | 2 | ✓ medium |
| References | excellent | isolated | none | ready | 0 | ✓ defer |
Retention Value¶
Purpose: Should I keep or delete this artifact?
Calculation: Based on network position, age, refinement, recent access
| Value | Criteria | Recommendation |
|---|---|---|
| essential | Hub + high refinement | Must retain |
| valuable | Referenced often + good health | Retain |
| marginal | Rarely accessed + peripheral | Review for archival |
| low | Not accessed in 6mo + isolated | Consider archiving |
| disposable | Transient form + low refinement | Safe to delete |
Example retention analysis:
| Note | Position | Last Access | Health | Links In | Retention | Action |
|---|---|---|---|---|---|---|
| Theoretical Framework | hub | 2 days ago | excellent | 23 | essential | Keep |
| 2023 Lit Review | connector | 45 days ago | good | 8 | valuable | Keep |
| Old Draft | peripheral | 180 days ago | fair | 2 | marginal | Archive? |
| Scratch Notes | isolated | 365 days ago | poor | 0 | low | Archive |
| Meeting Notes (2022) | isolated | 730 days ago | critical | 0 | disposable | Delete |
Why Layer 2 Matters¶
Without Layer 2: You have properties but no interpretation
With Layer 2: Properties become actionable insights
The same artifact can be interpreted differently in different contexts. A research note at refinement: 0.65 might be “ready” for personal use but “insufficient” for public sharing—all without storing duplicate metadata.
Layer 2 transforms static metadata into dynamic knowledge management.
Next Steps¶
Layer 3: Learn how dimensions trigger automated workflows and policy enforcement
Framework Overview: Return to J-Editorial
Practice: See Layer 2 calculations in action in the Case Study