Position Paper
Purpose
Answers: What do we think about this, why should the audience agree, and what would make us wrong? It takes a side. It is not tied to one client.
Example
Show a worked example of this artifact
---
ddx:
id: PP-001
type: position-paper
authoring:
home: repo
links:
- {id: TA-001, kind: supported_by, rev: example}
- {id: component-profile-python-reusable, kind: supported_by, rev: example}
recommendations:
- subject: component-profile-python-reusable
label: Python
context: repository-tooling
stance: conditional
conditions: The repository already uses Python and no script needs a Node.js-only library.
rationale: One runtime is less to install and maintain than two, and the cited assessment finds the two comparable for text and file work.
based_on: [{assessment: TA-001, criteria: [text-and-file-handling]}]
since: 2026-11-06
review_by: 2027-02-06
weights:
- criterion: text-and-file-handling
weight: decisive
reason: Repository tooling is mostly reading and rewriting text files.
- criterion: dependency-isolation
weight: minor
reason: Tooling scripts here lean on the standard library.
---
# PP-001: New repository tooling should default to Python
## Thesis
**Thesis**: New command-line tooling in a repository that already uses Python
should be written in Python, not Node.js, unless a script needs a Node.js
library with no equivalent.
## Audience and Stakes
Maintainers choosing a runtime for a new tooling script. A second runtime in
a repository adds installation and upkeep for every contributor.
## Decision Criteria
| Criterion | Weight | Why |
|-----------|--------|-----|
| Text and file handling | Decisive | Repository tooling is mostly reading and rewriting text files. |
| Dependency isolation | Minor | Tooling scripts here lean on the standard library. |
## Argument
1. Both runtimes handle text and file work comparably on the cited
assessment. [TA-001, Comparison]
2. A repository with one runtime has less to install and maintain than one
with two. Author's judgment.
3. So the existing runtime wins unless a library requires the other. Author's
judgment.
## Objections and Answers
| Objection | Answer | Evidence |
|-----------|--------|----------|
| The team already writes JavaScript | Familiarity favors Node.js for that team; the thesis assumes the repository's existing runtime is Python | Author's judgment |
| Distribution of a single script may differ | The assessment has no finding on distribution; the thesis does not rely on it | TA-001, Contradictions and Gaps |
## Recommendations
| Technology | Stance | Context | Conditions | Based on |
|------------|--------|---------|------------|----------|
| Python | Use with conditions (Proposed) | repository-tooling | The repository already uses Python and no script needs a Node.js-only library. | TA-001 |
## Limits of the Position
The paper does not claim Python is better in general.
| Condition | Option that wins | Evidence |
|-----------|------------------|----------|
| The repository's existing runtime is Node.js | Node.js | Author's judgment: argument step 2 favours whichever runtime is already there |
| A script needs a library that exists only for Node.js | Node.js | Author's judgment |
## Transition Path
Existing Node.js scripts stay as they are. The position covers new tooling
only, so nothing is rewritten.
## Evidence
| Reference | Kind | Revision | Used for |
|-----------|------|----------|----------|
| TA-001 | Technology assessment | example | Argument step 1 |Reference
| Activity | Discover — Validate that an opportunity is worth pursuing before committing to a development cycle. |
|---|---|
| Default location | docs/helix/00-discover/position-paper-PP-{number}-{subject}.md |
| Requires | None |
| Enables | None |
| Informs | Decision Brief Deliverable |
| Generation prompt | Show the full generation prompt |
| Template | Show the template structure |
Innsigle seal: model-primary by HELIX
The signature covers the markdown source of this page, not these HTML bytes. This page quotes that seal; verify it against the source file.
- Composition
- model-primary
- Issuer
- HELIX
helix - Signing key
ed25519:b0865d76d834a52c48506414d16f4e5a(build key)- Signed source
artifact-types/discover/position-paper.md- Signed
- 2026-11-16T15:52:45Z
- Content digest
sha256:5c485753…620958d2
This build key is endorsed by the human key for build signing; the signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-11-16T15:52:45Z",
"issuer": {
"id": "helix",
"name": "HELIX",
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"key_url": "https://documentdrivendx.github.io/helix/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/helix/artifact-types/discover/position-paper/",
"digest": {
"alg": "sha256",
"value": "5c48575324c0eba75a5e9b61386dc49d1b55a75f7226a22ac3236bde620958d2"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "model-primary",
"ingredients": [
{
"kind": "model",
"name": "Claude",
"role": "draft"
},
{
"kind": "tool",
"name": "sloptimizer",
"role": "rewrite"
},
{
"kind": "human",
"name": "operator",
"role": "structure-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:b0865d76d834a52c48506414d16f4e5a",
"alg": "ed25519",
"sig": "Oc_zeRoL2ymxdOcOgQSkXm1h6llDUVJlAZJclZFbE5wUQdET1zu9EtQsXxXi1b0a0O7enWXfwwkEczmg9Z-mDg",
"signed_at": "2026-11-16T15:52:45Z"
}
]
}