You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8
+
9
+
## Our Standards
10
+
11
+
Examples of behavior that contributes to a positive environment for our community include:
12
+
13
+
- Demonstrating empathy and kindness toward other people
14
+
- Being respectful of differing opinions, viewpoints, and experiences
15
+
- Giving and gracefully accepting constructive feedback
16
+
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
+
- Focusing on what is best not just for us as individuals, but for the overall community
18
+
19
+
Examples of unacceptable behavior include:
20
+
21
+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
22
+
- Trolling, insulting or derogatory comments, and personal or political attacks
23
+
- Public or private harassment
24
+
- Publishing others' private information, such as a physical or email address, without their explicit permission
25
+
- Other conduct which could reasonably be considered inappropriate in a professional setting
26
+
27
+
## Enforcement Responsibilities
28
+
29
+
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
32
+
33
+
## Scope
34
+
35
+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
36
+
37
+
## Enforcement
38
+
39
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at eros@blackdream.ai. All complaints will be reviewed and investigated promptly and fairly.
40
+
41
+
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
42
+
43
+
## Enforcement Guidelines
44
+
45
+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
46
+
47
+
### 1. Correction
48
+
49
+
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
50
+
51
+
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
52
+
53
+
### 2. Warning
54
+
55
+
**Community Impact**: A violation through a single incident or series of actions.
56
+
57
+
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
58
+
59
+
### 3. Temporary Ban
60
+
61
+
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
62
+
63
+
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
64
+
65
+
### 4. Permanent Ban
66
+
67
+
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
68
+
69
+
**Consequence**: A permanent ban from any sort of public interaction within the community.
70
+
71
+
## Attribution
72
+
73
+
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
74
+
75
+
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
76
+
77
+
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
<palign="center"><strong>A time first language and toolchain for hybrid neuromorphic classical systems.</strong></p>
2
6
3
-
Converge is a **time‑first programming language + toolchain** for building **hybrid neuromorphic–classical systems**: spiking networks, event streams, synaptic plasticity, and the host code that orchestrates them.
7
+
## What Converge is
4
8
5
-
It’s inspired by the *whole‑stack audacity* of projects like TempleOS/HolyC — not in aesthetics, but in ethos:
9
+
Converge is a time first programming language and compiler toolchain for hybrid neuromorphic classical systems. It targets spiking networks event streams synaptic plasticity and the host code that orchestrates them.
6
10
7
-
-**One coherent stack** you can hold in your head: language → compiler → IR → simulator → hardware backends.
8
-
-**Explicitness over magic**: time, units, delays, learning rules, and IO are first‑class.
9
-
-**Inspectable artifacts**: compilation emits human‑readable IR and deterministic reports.
11
+
It’s built around a simple insistence. Time isn’t metadata, it’s the program. Converge treats events delays and units as first class so you can compile the same intent into simulation interchange and hardware backends without rewriting the meaning.
10
12
11
-
Status: **pre‑α** (this repo is the start of the compiler/runtime).
13
+
Converge emits a canonical intermediate form called CVIR and it’s being shaped to align with NIR for ecosystem interchange. It’s early. The direction is not.
12
14
13
-
---
15
+
Status: pre alpha.
14
16
15
-
## Why this exists
17
+
## Thesis
16
18
17
-
Neuromorphic systems are arriving as **heterogeneous fabrics** (digital SNN chips, mixed‑signal accelerated-time systems, event-based sensors, and hybrid cloud access), and they increasingly live inside **classical control loops**. The painful part is not “writing a network” — it’s:
19
+
Neuromorphic systems don’t arrive as a single chip and a single SDK. They arrive as fabrics. You’ve got eventbased sensors, host control loops, routing constraints, quantization rules and timing jitter. If your program can’t name time precisely, you’ll be debugging folklore.
18
20
19
-
-**Time semantics** (discrete vs event-driven; delays; scheduling).
20
-
-**Hardware partitioning** (what runs on the host vs the neuromorphic fabric).
21
-
-**Interchange** between ecosystems (simulation, training, deployment).
22
-
-**Reproducibility** (randomness, quantization, routing constraints, and timing).
21
+
Converge is not a Python SNN library replacement. It’s a compiler toolchain that makes time explicit, makes artifacts inspectable and keeps execution deterministic enough to ship.
23
22
24
-
Converge’s bet: treat *time and events as the IR*, then compile down into whatever “fabric” you have.
23
+
## Design principles
25
24
26
-
---
25
+
1. Time is explicit in source and in IR.
26
+
2. Units are part of meaning and they can’t be shrugged off.
27
+
3. Determinism is a feature, not a nice to have.
28
+
4. If you can’t inspect it, you can’t deploy it.
29
+
5. Hardware comes later, semantics come first.
30
+
6. Interop is mandatory, not aspirational.
27
31
28
-
## The Converge stack (current direction)
32
+
## Architecture
29
33
30
34
```mermaid
31
35
flowchart LR
@@ -39,102 +43,38 @@ flowchart LR
39
43
E --> E4["hw targets (THOR / SpiNNaker2 / BrainScaleS-2)"]
40
44
```
41
45
42
-
**CVIR** is intentionally shaped to align with **NIR (Neuromorphic Intermediate Representation)** for ecosystem interchange.
46
+
Today you’ve got the front end plus a validator and a CVIR JSON emitter. Next you’ll get a deterministic simulator core then an interchange pipeline and finally hardware codegen.
43
47
44
-
---
48
+
## Quick start
45
49
46
-
## Language at a glance (fabric DSL)
47
-
48
-
Converge’s “fabric” layer is declarative: you describe neuron models, populations, connectivity, learning rules, and time.
49
-
50
-
```converge
51
-
neuron LIF {
52
-
tau_m = 20 ms
53
-
v_th = 1.0 V
54
-
}
55
-
56
-
layer Input[100] : LIF
57
-
layer Hidden[300] : LIF
58
-
layer Output[10] : LIF
59
-
60
-
connect Input -> Hidden { w = Uniform(-1.0, 1.0) d = Normal(1 ms, 0.1 ms) }
61
-
connect Hidden -> Output { w = Uniform(-1.0, 1.0) d = Normal(1 ms, 0.1 ms) }
62
-
63
-
run for 1 s
64
-
```
65
-
66
-
**Important:** the compiler/runtime will ultimately support both *event-driven* and *clocked* execution, but the semantics will remain *time-explicit* in source and IR.
67
-
68
-
---
69
-
70
-
## Quick start (today)
71
-
72
-
You need Rust (`rustc`/`cargo`).
50
+
You need Rust stable. Minimum supported Rust is 1.92.
73
51
74
52
```bash
53
+
cargo test
75
54
cargo run -p converge-cli -- check examples/hello.cv
76
55
cargo run -p converge-cli -- ast examples/hello.cv
56
+
cargo run -p converge-cli -- cvir examples/hello.cv
77
57
```
78
58
79
-
---
80
-
81
-
## Scope (what Converge is / isn’t)
82
-
83
-
Converge is not “yet another Python SNN library”. It’s a **compiler toolchain** meant to:
84
-
85
-
- Represent neuromorphic programs in a **hardware-agnostic** but *timing-precise* IR.
86
-
-**Partition** across a host CPU/GPU and neuromorphic fabric (hybrid arrays).
-**NIR (Neuromorphic Intermediate Representation)** as the interchange layer between frameworks/hardware.
107
-
-**Nengo**, **Brian2**, **Norse**, **snnTorch** (simulation/training ecosystems Converge can exchange with via IR and codegen).
108
-
109
-
See `docs/references.md` for links and short notes.
110
-
See `docs/spec.md` for the current accepted grammar (pre‑α).
111
-
112
-
---
113
-
114
-
## Security & robustness (responsible research)
115
-
116
-
Neuromorphic systems need the equivalent of “fuzzing + fault injection + timing adversaries”.
117
-
Converge intends to support **pathology-inspired robustness testing** (e.g., timing jitter, spike corruption, routing congestion, state rollback) as *first-class simulation modes*.
118
-
119
-
This is for defensive engineering and scientific study. No “malware DSL” lives here.
59
+
## Docs
120
60
121
-
---
61
+
1.`docs/spec.md` current accepted grammar and validation rules
62
+
2.`docs/references.md` curated anchors for hardware and interchange
Converge is conceived by Eros and it’s being built in open collaboration with AI tooling. You’ll see that stance in the artifacts. The repo is designed to be read, not just executed.
130
69
131
-
---
70
+
## Contributing
132
71
133
-
## License
72
+
Read `CONTRIBUTING.md` then pick something small and make it sharp. If you add syntax you’ll add tests and you’ll keep the IR stable.
134
73
135
-
MIT. See `LICENSE`.
74
+
## Security
136
75
137
-
## Contact
76
+
Read `SECURITY.md` for reporting. Converge will support defensive robustness testing and fault injection. It won’t ship offense code.
138
77
139
-
Open an issue, or email eros@blackdream.ai.
78
+
## License and contact
140
79
80
+
MIT. See `LICENSE`. Open an issue or email eros@blackdream.ai.
0 commit comments