How to Submit Ideas to LMRuntime

Full report

On this page

Executive summary

I audited LMRuntime.com directly and used Teleodynamic.com as a contextual cross-reference because the LMRuntime site explicitly describes its governance as “Teleodynamic-informed,” while both sites point to the same public owner contact, Michael Kappel. The most important finding is straightforward: I did not find a public idea portal, feature-request form, GitHub issue tracker, community forum, or public LMRuntime repository. Instead, LMRuntime currently exposes a single official human contact path centered on its /contact/ page, which publishes an email address and phone number and explicitly invites inquiries about LMRuntime, corrections, collaboration, press, and security routing. LMRuntime’s own status and release-discipline pages also say public GitHub and NuGet links are intentionally being withheld until validation, licensing, and release evidence are settled.

Teleodynamic.com does not appear to publish an LMRuntime contribution workflow by name in the pages I audited. In fact, the Teleodynamic pages I checked did not contain an explicit “LMRuntime” mention, and Teleodynamic’s own “source boundary” language says claims should route back to the site that owns them rather than being absorbed by Teleodynamic. That makes Teleodynamic useful mainly as process context and as a corroborating fallback contact surface, not as the authoritative LMRuntime submission system.

Practically, the best current way to add an idea to LMRuntime is to send a well-structured email to the address published on the official LMRuntime contact page. The page itself tells you what to include for LMRuntime questions: the page, runtime area, model format, platform, and the specific question or correction. LMRuntime’s governance page also shows the review style you should expect: explicit budgets, “no-op dominance,” human review before promotion, and evidence-before-claims. That suggests an idea framed as a bounded, testable proposal with evidence and constraints is more likely to receive serious consideration than a vague suggestion.

One caveat: the domain you supplied as Teleodyanmic.com returned a 502 error during retrieval. I therefore used Teleodynamic.com, which is the functioning official site matching the project name and content.

What the two sites currently expose

LMRuntime.com presents itself as a public documentation and status surface for a local-first C# runtime direction. Its top-level navigation exposes Runtime, Docs, Architecture, Evidence, Governance, Security, and Get Started, while the footer adds Licensing, Accessibility, Release Discipline, Link to This Work, and Contact. The home page describes the project as a source candidate rather than a publicly released package, emphasizes evidence-bounded claims, and points readers to Contact for project interaction.

The official LMRuntime contact page gives the clearest current intake mechanism. It explicitly says you can email or call Michael Kappel about LMRuntime, corrections, collaboration, press, or security routing, identifies email as “the best default” for project details and corrections, and publishes both the email address and phone number. The same page also links out to MikeKappel.com, LinkedIn, GitHub, and Facebook as owner-approved context channels.

At the same time, LMRuntime’s project-status and release-discipline pages make clear why there is no public repo workflow yet. Project Status says the site does not currently represent a generally available NuGet package, public package is “Not announced,” and users should use the contact path for collaboration, corrections, or source-access questions. Release Discipline says the site should link to GitHub or NuGet only after licensing, validation, package naming, and claim wording are settled.

Teleodynamic.com is broader and more process-heavy. Its home page and About page describe it as a public research and framing site with “source-routed” boundaries, meaning related-domain claims should point back to the domain that owns them. The Contact and Privacy pages show the same owner contact posture visible on LMRuntime: public email, phone, external profile links, no on-site contact form, no account system, and a warning not to send secrets through public channels.

Teleodynamic does provide useful contribution-style patterns even though it does not expose an LMRuntime-specific intake. Examples include:

• “New Content and Improvement files” belonging in agent-file-handoff buckets with visible disposition.
• A suggested issue packet format that includes node, trace, memory state, endpoint boundary, repair/no-op status, and exit condition.
• Static “reviewer finding intake” and “talkback” schemas that stage requests for human review without mutating canonical state.
• Explicit language that active ingestion is not claimed in some of these structured routes yet.

That is useful context because it shows how the ecosystem prefers ideas to be shaped: bounded, evidence-backed, reviewable, and safe to no-op if unclear.

Navigation map

The diagram below maps the public pages most relevant to idea submission and cross-reference context, based on the official navigation and sitemap pages.

graph TD
  subgraph LMRuntime.com
    LMHome["Home"]
    LMHome --> LMRuntime["Runtime Overview"]
    LMHome --> LMDocs["Documentation"]
    LMHome --> LMArch["Architecture"]
    LMHome --> LMEvidence["Evidence & Benchmarks"]
    LMHome --> LMGov["Governance"]
    LMHome --> LMSec["Security"]
    LMHome --> LMStart["Getting Started"]
    LMHome --> LMContact["Contact"]

    LMDocs --> LMStatus["Project Status"]
    LMDocs --> LMSource["Source Map"]
    LMDocs --> LMVal["Validation Ladder"]
    LMDocs --> LMLicense["Licensing"]
    LMDocs --> LMAccess["Accessibility"]
    LMDocs --> LMRelease["Release Discipline"]
    LMDocs --> LMGlossary["Glossary"]
  end

  subgraph Teleodynamic.com
    TDHome["Home"]
    TDHome --> TDAbout["About"]
    TDHome --> TDResources["Resources / HTML Sitemap"]
    TDHome --> TDContact["Contact"]
    TDHome --> TDPrivacy["Privacy"]
    TDHome --> TDAgent["Agent Start"]
    TDHome --> TDEcoLinks["Relevant Platform Links"]
    TDHome --> TDEcoMatrix["Relationship Matrix"]
    TDHome --> TDTalkback["Talisman Talkback"]
    TDHome --> TDIntake["Teleodynamic Intake Synthesis"]
  end

Two pages are especially valuable for understanding the current submission reality on LMRuntime. First, Contact is the active human route. Second, Status and Release Discipline explain why there is no repo-centric contribution path yet.

The annotated sketch below condenses the relevant LMRuntime contact-page elements into a submission-oriented view. It is based directly on official page text.

flowchart TD
  A["LMRuntime Contact page"] --> B["Email: mike@ns12.com"]
  A --> C["Phone: (708) 230-2304"]
  A --> D["Email is the best default for project details and corrections"]
  A --> E["Include: page, runtime area, model format, platform, specific question or correction"]
  A --> F["Use for LMRuntime, corrections, collaboration, press, security routing"]
  A --> G["Links out: MikeKappel.com, LinkedIn, GitHub, Facebook"]

Teleodynamic’s relevant cross-reference pattern is similar: no public form, no account-based intake, but a strong emphasis on structured, public-safe human review.

flowchart TD
  A["Teleodynamic Contact + Privacy"] --> B["Public email and phone"]
  A --> C["No on-site form"]
  A --> D["No account system"]
  A --> E["Do not send secrets"]
  A --> F["Include concise goal, public URL, project type, preferred next step"]
  A --> G["Structured patterns: issue packet, agent-file-handoff, talkback review"]

Official submission routes on LMRuntime

Direct idea submission by email

This is the strongest current method.

The official LMRuntime contact page says email is the best default for project details and corrections, and it publishes mike@ns12.com as the direct address. The same page says LMRuntime questions should include the page, runtime area, model format, platform, and the specific question or correction. Project Status reinforces that the contact path is the place to ask about access or corrections.

Step by step

1. Open the official LMRuntime Contact page.
2. Start an email to the published address.
3. Put the idea in a concrete subject line, for example: LMRuntime idea: deterministic benchmark receipt export.
4. In the body, include:

• the exact LMRuntime page you were reading,
• the runtime area affected,
• model format,
• platform,
• the proposal itself,
• why it matters,
• what evidence or examples support it,
• what a minimal first step would be.

1. Ask for the preferred next step: clarification, source-access discussion, or whether the idea should wait until repo/package release gates open.

Required account type

No site account is required. You only need access to an email account.

Formatting guidance

LMRuntime publishes only minimal formatting guidance, but its governance posture implies that better submissions are likely to be:

• evidence-backed,
• bounded in scope,
• explicit about constraints,
• clear about whether they are ideas, corrections, or release questions,
• acceptable to no-op if evidence is not yet sufficient.

Expected response time

No response-time commitment or SLA is published on LMRuntime.com.

Review or moderation policy

No public moderation queue is published. What is published is a conservative review philosophy: bounded action, no-op dominance, review before promotion, and evidence before claims. That is not a feature-request policy in the narrow sense, but it is the clearest available signal of how submitted ideas are likely to be screened.

Accessibility or UX-feedback submission

LMRuntime has a specific public path for accessibility-related problems, which can also be used for highly actionable UX issues on the site itself.

The Accessibility page says to report a problem by including the page URL, browser, device, assistive technology, expected result, and what happened, and directs users to Contact LMRuntime.com.

Step by step

1. Identify whether the idea is really an accessibility or UX defect rather than a runtime feature request.
2. Collect the requested context: page URL, browser, device, assistive technology if relevant, expected result, and what happened.
3. Send that information through the LMRuntime contact path.
4. Keep the report factual and avoid private data.

Required account type

None beyond email or phone.

Expected response time

Not stated.

Review or moderation policy

Known issues should be documented and repaired rather than hidden behind conformance language. That implies a fairly concrete defect-review posture for site accessibility concerns.

Security or sensitive correction routing

This is not an idea-submission path, but it matters because some “ideas” blur into security findings, disclosure concerns, or sensitive corrections.

The LMRuntime Contact page says not to publish exploit details in a public post and to follow the dedicated disclosure path first. The Security page says to use that page as the public contact point for security reports, corrections, and disclosure-boundary questions, and it references a canonical /.well-known/security.txt record pointing back to the policy page.

Step by step

1. If the submission involves a vulnerability, exploit path, or sensitive disclosure question, do not post it publicly.
2. Read the Security page first.
3. Use the LMRuntime contact path to route the issue privately.
4. Keep the message limited to evidence needed for triage.

Required account type

None beyond email or phone.

Expected response time

Not stated.

Review or moderation policy

Responsible disclosure is explicitly preferred. Sensitive internals are intentionally held back from public pages until release decisions are made.

Teleodynamic cross-references and what they imply

The key negative result is important: I did not find Teleodynamic pages that explicitly document an LMRuntime-specific contribution workflow. I checked the Teleodynamic home page, About, Resources, Contact, Privacy, and Relationship Matrix pages; none returned an explicit LMRuntime mention in the retrieved text.

That absence matters because Teleodynamic’s own About page says it is a source-routed public framing site and that claims should route back to the owning site rather than being absorbed into Teleodynamic authority. So even if Teleodynamic discusses governance ideas relevant to LMRuntime, it should not be treated as the authoritative LMRuntime submission endpoint.

What Teleodynamic does provide is a strong contextual model for how ideas should be packaged if you want them to land well with this ecosystem:

Teleodynamic says “New Content and Improvement files” belong in agent-file-handoff buckets and need visible disposition before broader work continues. It also says a useful issue copy should include the node, trace, memory state, endpoint boundary, repair/no-op status, and exit condition. Those are not public LMRuntime mechanisms, but they are excellent clues about the owner’s preferred review style: explicit context, explicit evidence, and explicit disposition.

Teleodynamic’s contact guidance is also directly relevant as a fallback channel. It says public email is appropriate for introductions, collaboration ideas, route feedback, and architecture questions; it is not a secure intake portal; and messages should include a concise goal, public URL, project type, and preferred next step. The Privacy page confirms there is no on-site form and that the public contact flow uses email, phone, and external profile links instead.

Finally, Teleodynamic’s more structured review routes are deliberately static and human-reviewed. Talisman Talkback describes a schema for proposed changes and clarifications, but it also says active ingestion is not claimed and that requests do not mutate canonical state by themselves. Reviewer-finding intake and talkback-review pages use the same pattern: copyable rows, review scaffolds, no active inbox guarantees, no automatic application. That tells you there is a strong review-first culture, but not a public self-service submission system you can rely on today.

Best practice for sending an idea now

The best current strategy is to use the official LMRuntime email route, but to structure your message in a way that fits both LMRuntime’s published intake hints and Teleodynamic’s broader review patterns. That means treating the submission as a concise, testable proposal rather than a brainstorm dump.

A good structure is:

A one-line idea name.

1. Title

The exact LMRuntime page and runtime area.

1. Where this applies

What is missing, confusing, risky, or useful.

1. Current limitation or opportunity

Examples, reproductions, comparable tools, or concrete workflow pain.

1. Evidence or trace

The smallest useful version first.

1. Proposed change

Model format, platform, compatibility concerns, evidence gaps, or reasons this may need to wait for release gates.

1. Boundaries and constraints

State what a reasonable “no-op for now” decision would be if the project is not ready. This aligns unusually well with the site’s published “no-op dominance” posture.

1. Review-friendly fallback

Here is a strong email template you can send now:

Subject: LMRuntime idea: [short feature name]

Hi Michael,

I’m writing with an LMRuntime idea related to:
- Page: [exact LMRuntime page]
- Runtime area: [e.g., validation, CLI, evidence, packaging, governance, docs]
- Model format: [e.g., GGUF]
- Platform: [Windows / Linux / macOS / CUDA / CPU]

Current limitation or opportunity:
[Describe the problem or opportunity in 2–4 sentences.]

Why this matters:
[Describe the practical developer value, correctness impact, or documentation value.]

Evidence / examples:
- [Repro step, observed gap, or comparable workflow]
- [Any benchmark, docs friction, or integration example]
- [Any risk or constraint]

Proposed minimal change:
[Describe the smallest useful first implementation or documentation step.]

Boundaries:
[I understand LMRuntime is currently documented as a source candidate and not a public package/repo release. If this should wait for a later release gate, a “not yet” answer is fine.]

Preferred next step:
[Clarify / keep on backlog / discuss source access / wait for public repo]

Thanks,
[Your name]

That template uses the exact intake cues LMRuntime publishes and adds the evidence/constraint language that matches its governance posture.

If the idea is more like a site defect, documentation gap, or accessibility issue, use this variant:

Subject: LMRuntime site issue: [short summary]

Hi Michael,

I found an issue on LMRuntime.com.

Page URL:
[page]

Environment:
- Browser:
- Device:
- OS:
- Assistive technology, if relevant:

Expected result:
[what should happen]

What happened:
[what actually happened]

Why it matters:
[accessibility, clarity, broken flow, inaccurate claim, etc.]

This report contains no private or sensitive information.

Thanks,
[Your name]

That follows the Accessibility page’s published problem-report fields.

If you want to lean into the broader Teleodynamic review style, you can also add a compact “issue packet” footer:

Review packet
- Node / area:
- Trace / observed path:
- Endpoint boundary:
- Repair suggestion:
- No-op fallback:
- Exit condition:

That mirrors the issue-copy pattern Teleodynamic publishes.

Alternatives, templates, and comparative assessment

Because LMRuntime currently lacks a public repo, forum, or feature-request form, the alternatives are mostly contact-route fallbacks rather than true submission systems. The table below ranks them by ease, reliability, and the likelihood that they reach meaningful review. Those ratings are my inference from channel specificity, public ownership, and the review posture described on the audited pages; they are not site-published scores.

Fallback outreach templates

Teleodynamic fallback email

Subject: Public-safe collaboration idea related to LMRuntime

Hi Michael,

I’m reaching out through the Teleodynamic contact route because I could not find a public LMRuntime issue tracker or feature-request form.

Concise goal:
[one sentence]

Public URL:
[relevant LMRuntime or Teleodynamic page]

Project type:
[feature idea / documentation correction / architecture question / collaboration]

Preferred next step:
[email reply / brief call / “wait until public repo” / point me to the right channel]

I am only including public-safe information.

Thanks,
[Your name]

This maps directly to the Teleodynamic contact instructions.

LinkedIn fallback DM

Hi Michael — I sent a short public-safe LMRuntime idea by email and wanted to confirm I used the right channel. I did not find a public LMRuntime issue tracker or form. If there is a better submission route, I’d appreciate a pointer. Thanks.

This is appropriate because LinkedIn is explicitly linked as a professional profile/context channel from LMRuntime and Teleodynamic contact surfaces.

ICANN/RDAP escalation note

If an official published contact route becomes unavailable, ICANN’s lookup tool is the official starting point for current registration data lookup, but results may be redacted and are not guaranteed to reveal a personal registrant contact. In this audit, I did not retrieve domain-specific registrant details for LMRuntime.com or Teleodynamic.com.

Bottom line

If your goal is to add an idea to LMRuntime today, the evidence supports one clear primary recommendation: use the official LMRuntime contact email, and send a tight, review-friendly proposal that includes the page, runtime area, model format, platform, concrete idea, supporting evidence, and a minimal first step. That is the only clearly official, publicly visible submission route I found on LMRuntime itself.

Teleodynamic is useful mainly as a process lens. It suggests the owner prefers submissions that are public-safe, source-routed, bounded, evidence-backed, and explicit about no-op outcomes and human review. But Teleodynamic does not appear to host an LMRuntime contribution workflow by name, and its own source-boundary language argues against treating it as the authoritative intake surface for LMRuntime ideas.

What remains unavailable or unconfirmed is just as important: I found no public form, no public forum, no public LMRuntime GitHub repository, no public issue tracker, no declared response times, and no public moderation SLA. Those absences are consistent with LMRuntime’s current status as a source candidate whose public package/repo release is intentionally gated.