RESPONSIBLE USE
Experimental artifacts require cautious use.
The public pilots are small base-completion models with documented reliability limits. Echelon has no trained public model. None of these artifacts should be treated as a production assistant.
EXCLUDED USES
PublishedDo not treat experimental completions as decisions.
- Medical, legal, financial or safety-critical decisions
- Automated decisions about people, eligibility, employment or access
- Unsupervised factual publication or authoritative advice
- Security-sensitive automation or operation of critical infrastructure
- Any use that assumes instruction following, chat alignment or factual reliability
KNOWN BEHAVIOR
Limits observed in the public record.
Factual inconsistency
Completions may be grammatically structured while making incorrect claims.
Repetition
The pilots may repeat tokens, phrases or structures instead of developing a coherent continuation.
Incomplete or incoherent text
Outputs may stop abruptly, drift from the prompt or lose semantic continuity.
No instruction or chat alignment
The pilots are base-completion artifacts. No chat template, refusal behavior or instruction-following capability is promised.
UNMEASURED RISKS
Not measuredNo safety evaluation is inferred.
- Bias across demographic, cultural or political groups
- Toxic, harmful or illegal-content generation
- Memorisation and reproduction of source material
- Personal-data leakage
- Prompt-injection or adversarial robustness
- Misuse potential and model-specific security behavior
ARTIFACT SAFETY
Treat files and code as untrusted.
- Verify repository revision, filename, byte size and checksum before use.
- Treat model files, datasets, scripts and conversion tools as untrusted inputs.
- Keep remote-code execution disabled unless the exact code has been reviewed.
- Run unfamiliar training or inference workloads without host secrets and with limited privileges.
- Do not publish raw outputs as facts without independent verification.
REPORTING
Use the right channel.
Model behavior or documentation
Use a public GitHub issue when the report contains no private data or security-sensitive details.
Open reporting guidanceWebsite security
Follow the private vulnerability-reporting process. Do not publish secrets or exploit details in a public issue.
Open reporting guidancePrivacy, rights or sensitive material
Email the project directly and include only the information necessary to identify the concern.
Open reporting guidanceDOCUMENTATION DIRECTORY
Continue through the evidence.
Every section keeps public evidence, configured targets and missing information visibly separate.