Skip to content
View Sigilith's full-sized avatar
🏠
Working from home
🏠
Working from home

Block or report Sigilith

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
sigilith/README.md

Ky Nash

Structural analysis · Runtime governance · Reproducible testing

I develop Sigilith, a research framework for analysing the structure of symbolic systems, and ThreeLineage, a project exploring governed execution and auditable runtime behaviour.

My focus is on making technical claims inspectable: clear assumptions, bounded experiments, explicit failure cases, and evidence tied to the code that produced it.

Open to scoped, remote work: Python tooling, regression tests, technical documentation, and research reproducibility.

Discuss a project · Read the primary paper


Start with the research

Sigilith studies structural properties of symbolic systems through canonical segmentation, behaviour-preserving transformations, metric extraction, structural signature constraints, and classification.

The research concerns structure. Structural similarity alone does not establish a text's meaning, language, or decipherment.

Primary paper
Nash, K. (2026). A reproducible structural analysis of the Voynich manuscript via Sigilith v1.0.
DOI and publication record · PDF in this repository · Citation metadata

This repository is a research entry point containing the paper and citation metadata. It does not currently include an executable reproduction package.

Runtime governance work

ThreeLineage / TraceGuard is my development work on execution boundaries, authenticated requests, audit records, and recovery behaviour.

The questions guiding that work are concrete:

  • What is authorised to execute, and what happens when authorisation fails?
  • Can an audit record be checked for alteration or missing links?
  • What happens when a key is revoked, a request is replayed, or a process restarts?
  • Which guarantees depend on the operating environment?

Runtime results need their own source, test commands, commit identifiers, and stated limitations. The research paper above is not a security certification of the runtime.

How I approach contributions

  1. Agree the problem and acceptance criteria.
  2. Reproduce the failure or establish the baseline.
  3. Make a focused change with a regression test.
  4. Record the exact commit, commands, results, and remaining limitations.

Verification should be repeatable by a reviewer. A project name or generated comment is not test evidence.

Research catalogue

The following DOI links are retained from the original research index.

Collection Publication records
Core framework Record 1 · Record 2
Case studies Record 1 · Record 2 · Record 3
Further case studies Record 4 · Record 5 · Record 6

Work with me

For a remote project, send the problem, repository or sample input, expected deliverable, budget, and deadline to kynash1@outlook.com.

K. Nash
ThreeLineage

Pinned Loading

  1. Sigilithlabs/AXIOMOS Sigilithlabs/AXIOMOS Public

    AXIOMOS is an explainable governance and measurement platform that combines deterministic policy evaluation, signed evidence, replay validation, calibration, and transparent runtime auditing into a…

    Python 1