Skip to content

Add ENLIL: open-source multi-agent LLM council with PQC-signed decisions - #352

Open
conchaestradamiguelangel-droid wants to merge 4 commits into
Jenqyang:mainfrom
conchaestradamiguelangel-droid:add-enlil-multi-agent
Open

Add ENLIL: open-source multi-agent LLM council with PQC-signed decisions#352
conchaestradamiguelangel-droid wants to merge 4 commits into
Jenqyang:mainfrom
conchaestradamiguelangel-droid:add-enlil-multi-agent

Conversation

@conchaestradamiguelangel-droid

Copy link
Copy Markdown

Adding ENLIL to Multi-Agent Task Solver Projects.

9 AI models deliberate in parallel on every query, returning consensus + dissenting views. Every decision signed with ML-DSA-87 (NIST FIPS 204 post-quantum). BYOK, self-hosted, GPL v3.

GitHub: https://github.com/conchaestradamiguelangel-droid/enlil

@Jenqyang

Jenqyang commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Decision: Not ready to merge yet.

Reason:

  1. Candidate may fit, but the current entry and README lean on promotional framing and fixed named model claims.
  2. The standalone OSS value should be clearer given the OpenRouter/BYOK dependency and very early adoption signals.

Next step: Rewrite the entry in neutral technical terms and clarify what remains useful in the self-hosted OSS artifact independent of the hosted model gateway.

Per maintainer feedback: removes promotional framing, clarifies that
the orchestration/aggregation/signing pipeline is the standalone OSS
value, independent of which LLM backend is configured via OpenRouter.
@conchaestradamiguelangel-droid

Copy link
Copy Markdown
Author

Thanks for the specific feedback. Rewrote the entry: removed the promotional framing and the fixed model-count claim, and reworded to make clear the orchestration/aggregation/signing pipeline is the standalone OSS artifact -- it works with any OpenAI-compatible endpoint, not tied to a specific model set. OpenRouter/BYOK is just the transport layer for model access, not a hard dependency of the core logic.

@Jenqyang

Jenqyang commented Jul 8, 2026

Copy link
Copy Markdown
Owner

Decision: Still not ready to merge.

Reason:

  1. The rewritten line is better, but it is still long and provider/example heavy for the README.
  2. The upstream README still reads as claims-heavy/promotional for a very new project with limited external evidence.
  3. Under the stricter curation bar, this needs clearer standalone OSS usage evidence and a shorter neutral description before inclusion.

Next step: Keep the entry concise and technical, avoid branded/mythic framing and provider callouts, and add clearer docs or usage evidence that show the project is ready for a curated agent list.

@conchaestradamiguelangel-droid

Copy link
Copy Markdown
Author

Shortened the ENLIL line and dropped the provider/standard specifics (OpenRouter/BYOK, ML-DSA-87/NIST FIPS 204) as requested — now matches the style of the other one-line entries. Ready for another look.

@conchaestradamiguelangel-droid

Copy link
Copy Markdown
Author

Updated the entry per your feedback — shorter and purely functional, no provider references or framing:

Let me know if you need any further adjustments.

@conchaestradamiguelangel-droid

Copy link
Copy Markdown
Author

Following up — the entry has been at the shortened, neutral one-liner (no provider references, no framing) since the last update on 07/09. Happy to adjust further if there is still something specific blocking it, otherwise just flagging for another look when you have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants