embeddenator 0.20.0-alpha.1

Sparse ternary VSA holographic computing substrate
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93

# Architecture Decision Records (ADR)

This directory contains Architecture Decision Records (ADRs) documenting significant architectural decisions made in the Embeddenator project.

## What is an ADR?

An Architecture Decision Record captures an important architectural decision made along with its context and consequences. ADRs help:
- Understand the rationale behind design choices
- Onboard new team members
- Prevent repeating past discussions
- Document architectural evolution over time

## ADR Format

Each ADR follows this structure:

- **Status**: Proposed | Accepted | Deprecated | Superseded
- **Date**: When the decision was made
- **Context**: The issue motivating this decision
- **Decision**: The change being proposed or made
- **Consequences**: Positive, negative, and neutral impacts

## Current ADRs

| ID | Title | Status | Date |
|----|-------|--------|------|
| [ADR-001](ADR-001-sparse-ternary-vsa.md) | Choice of Sparse Ternary VSA | Accepted | 2025-12-15 |
| [ADR-002](ADR-002-multi-agent-workflow-system.md) | Multi-Agent Workflow System | Accepted | 2025-12-15 |
| [ADR-003](ADR-003-self-hosted-runner-architecture.md) | Self-Hosted Runner Architecture | Accepted | 2025-12-22 |
| [ADR-004](ADR-004-holographic-os-container-design.md) | Holographic OS Container Design | Accepted | 2025-12-15 |
| [ADR-005](ADR-005-hologram-package-isolation.md) | Hologram-Based Package Isolation and Factoralization | Proposed | 2025-12-23 |
| [ADR-006](ADR-006-dimensionality-sparsity-scaling.md) | Dimensionality and Sparsity Scaling in Holographic Space | Proposed | 2025-12-23 |
| [ADR-007](ADR-007-codebook-security.md) | Codebook Security and Reversible Encoding | Proposed | 2025-12-23 |
| [ADR-008](ADR-008-bundling-semantics-and-cost-aware-hybrid.md) | Bundling Semantics and Cost-Aware Hybrid | Proposed | 2026-01-01 |
| [ADR-009](ADR-009-deterministic-hierarchical-artifacts.md) | Deterministic Hierarchical Artifact Generation | Accepted | 2026-01-01 |
| [ADR-010](ADR-010-router-shard-bounded-indexing.md) | Router+Shard Architecture for Bounded Node Indexing | Accepted | 2026-01-01 |
| [ADR-011](ADR-011-multi-input-namespace-management.md) | Multi-Input Ingest and Namespace Management | Accepted | 2026-01-01 |
| [ADR-012](ADR-012-reusable-codebook-index.md) | Reusable Codebook Index for Query Performance | Accepted | 2026-01-01 |
| [ADR-013](ADR-013-hierarchical-manifest-format.md) | Hierarchical Manifest Format and Versioning | Accepted | 2026-01-01 |
| [ADR-014](ADR-014-incremental-updates.md) | Incremental Updates | Accepted | 2026-01-01 |
| [ADR-017](ADR-017-phase2a-component-extraction.md) | Phase 2A Component Extraction Strategy | Accepted | 2026-01-04 |

## Creating a New ADR

When making a significant architectural decision:

1. Copy the template below
2. Number it sequentially (ADR-00X)
3. Fill in all sections
4. Submit for review via pull request
5. Update this README's table

### Template

```markdown
# ADR-XXX: [Title]

## Status

[Proposed | Accepted | Deprecated | Superseded by ADR-YYY]

## Date

YYYY-MM-DD

## Context

[Describe the issue or situation requiring a decision]

## Decision

[Describe the decision and its rationale]

## Consequences

### Positive
- [List positive outcomes]

### Negative
- [List negative outcomes and trade-offs]

### Neutral
- [List neutral impacts or considerations]

## References

- [Links to related documentation, issues, or PRs]
```

## References

- [Documenting Architecture Decisions](https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions) - Michael Nygard
- [ADR GitHub Organization](https://adr.github.io/) - Tools and resources