feat: Add P.A.R.A. Method semantic anchor

[Copilot]

Adds Tiago Forte's P.A.R.A. Method (Projects, Areas, Resources, Archive) as a new semantic anchor — a tool-agnostic knowledge organization framework that categorizes information by actionability.

Changes

• docs/anchors/para-method.adoc — English anchor: four PARA categories, actionability principle, tool-agnostic nature, and when-to-use guidance
• docs/anchors/para-method.de.adoc — German translation
• website/public/data/anchors.json — New entry under documentation category; proponent Tiago Forte; tags: knowledge-management, personal-productivity, second-brain; related anchors: diataxis-framework, todotxt-flavoured-markdown
• skill/semantic-anchor-translator/references/catalog.md — New entry in the Documentation section so AI agents can recognize and suggest P.A.R.A.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Anchor Proposal]: Tiago Forte's P.A.R.A. Method</issue_title>
<issue_description>### Proposed Term

P.A.R.A.

Context (Optional)

A tool agnostic method to organize notes according their actionability (Projects, Areas, Resources, Archive) by Tiago Forte.

Pre-submission Checklist

• I have searched existing anchors and this term is not already included
• This term refers to a well-established concept (not something I invented)</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Anchor Proposal]: Tiago Forte's P.A.R.A. Method #346

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[raifdmueller]

Analysis of Proposed Anchors

Evaluated against the quality criteria: Precise, Rich, Consistent, Attributable.

Summary

PR	Anchor	Tier	Recommendation	Rationale
#354	P.A.R.A. Method	3	⚠️ Discuss	Rich and attributable (Tiago Forte), but knowledge management — not SE methodology. Extends catalog scope.
#355	PERT	2	✅ Accept	Classic estimation technique (1958), precise formula, well-established. Tier 2 is correct — useful but niche.
#356	Spec-Driven Development	3	⚠️ Discuss	Relevant to our workflow doc, but is it an established anchor or an emerging practice? Proponents listed (Swagger, Thoughtworks) are not the originators of the term.
#357	Explicit Contract Surface	3	❌ Reject	Not an established term — it's a combination of existing patterns (ACL, DTOs, contract-first). Proponents listed (Evans, Martin, Fowler) didn't coin this term. Fails "Attributable" criterion.
#358	Vertical Slice Architecture	3	✅ Accept	Well-established (Jimmy Bogard), precise, rich. Tier 3 is justified — complements Clean/Hexagonal Architecture.
#359	GRASP	3	✅ Accept	Classic OO patterns (Craig Larman), 9 well-defined patterns. Tier 3 justified — foundational, widely taught.
#360	KISS	1	⚠️ Discuss	Tier 1 is correctly assigned by Copilot! KISS lacks definition depth — "keep it simple" is a directive, not a methodology. Same problem as YAGNI (also Tier 1). But it's so widely referenced that excluding it feels wrong.

Detailed Analysis

#354 P.A.R.A. Method — ⚠️ Discuss

• Precise: Yes — four clear categories (Projects, Areas, Resources, Archive)
• Rich: Moderate — primarily an organizational framework, less rich than Diataxis
• Consistent: Yes — well-defined by Forte
• Attributable: Yes — Tiago Forte, "Building a Second Brain"
• Concern: Extends catalog beyond SE into personal productivity. Is that in scope?

#355 PERT — ✅ Accept

• Precise: Very — concrete formula (O+4M+P)/6, network diagrams, critical path
• Rich: Yes — connects estimation, scheduling, probability, risk
• Consistent: Yes — 65+ years of established usage
• Attributable: Yes — Malcolm, Roseboom, Clark, Fazar (1958)
• Tier 2 correct: Useful but specialized (project planning, not daily coding)

#356 Spec-Driven Development — ⚠️ Discuss

• Precise: Moderate — the term is used differently by different people (API-first vs. formal specs vs. our workflow doc)
• Rich: Yes — connects to BDD, TDD, contract-first, verification
• Consistent: Weak — no single canonical definition
• Attributable: Weak — Swagger/Thoughtworks are not the originators; the term is emergent
• Concern: We have a whole workflow document about this. Making it an anchor could create circular references. Also, our evaluation showed EARS (similar domain) scores poorly.

#357 Explicit Contract Surface — ❌ Reject

• Precise: Moderate — describes a pattern but the name is not established
• Rich: Yes — connects ACL, DTOs, mapping, DIP
• Consistent: No — this is not a recognized term in the literature
• Attributable: No — Evans/Martin/Fowler did not coin this term
• This is a design practice, not a semantic anchor. It combines existing anchors (Clean Architecture, DDD, SOLID DIP) but doesn't add a new activation.

#358 Vertical Slice Architecture — ✅ Accept

• Precise: Yes — clear distinction from layered architecture
• Rich: Yes — connects to CQRS, feature cohesion, screaming architecture
• Consistent: Yes — Jimmy Bogard's talks and blog posts are canonical
• Attributable: Yes — Jimmy Bogard
• Tier 3 justified: A well-known alternative to Clean/Hexagonal that LLMs should know

#359 GRASP — ✅ Accept

• Precise: Very — 9 named patterns with clear definitions
• Rich: Yes — foundational OO design patterns, connects to SOLID, GoF
• Consistent: Yes — Craig Larman's "Applying UML and Patterns" is canonical
• Attributable: Yes — Craig Larman
• Tier 3 justified: Standard curriculum material, widely taught

#360 KISS — ⚠️ Discuss

• Precise: Low — "keep it simple" is a directive, not a methodology
• Rich: Low — doesn't activate multiple interconnected concepts
• Consistent: Mixed — everyone agrees on the principle but not on what "simple" means
• Attributable: Yes — Kelly Johnson (Lockheed Skunk Works)
• Tier 1 correctly assigned: Same tier as YAGNI and TIMTOWTDI. Copilot got this right!
• Question: We reference KISS in the workflow doc (AGENTS.md conventions). Rejecting it would be inconsistent.

[arampp]

looks good to me

[raifdmueller]

Thanks for proposing P.A.R.A.! Tiago Forte's framework is well-defined, attributable, and clearly meets the "Precise", "Rich", and "Consistent" criteria.

Recommendation: merge, but consider Tier 2 instead of Tier 3.

The one question is scope — P.A.R.A. is a knowledge organization framework, not a software engineering methodology per se. That said, developers use it for organizing project documentation, architecture notes, and technical knowledge, so it fits naturally alongside Diataxis and Docs-as-Code in the documentation category.

Tier 2 might be more appropriate than Tier 3 because it's less directly applicable to coding workflows than our core SE anchors. But that's a minor point — the anchor itself is solid.

Evaluation results: 100% on Claude, GPT-4o, and Mistral Large (L1 Recognition).

[rdmueller]

@raifdmueller I do agree that most anchors are currently about software development, but I think we should collect all sorts of anchors. If needed, we should open a new category.

[raifdmueller]

Agreed! The catalog should not be limited to software engineering. Semantic anchors work across any domain where LLMs have deep knowledge — and P.A.R.A. clearly qualifies.

A new category like knowledge-management or personal-productivity would keep the MECE structure clean. P.A.R.A. is currently filed under documentation, which works but might get crowded as we add more non-SE anchors.

Recommendation: merge as-is. We can refine the category later if needed.