Releases: gitGyro-Dev/gyroauth
Release list
GyroAuth v2.1.0 — Guarded Criterion Trajectories and Research Demo
GyroAuth v2.1.0 — Guarded Criterion Trajectories and Research Demo
Summary
GyroAuth v2.1.0 adds the guarded criterion-update research track, deterministic proof-of-concept scenarios, publication artifacts, and a minimal GitHub Pages research demo.
This release preserves the foundational definition:
Authentication = Stability-based Selection over State Convergence
and makes the following distinctions explicit:
Subject Evaluation
!=
Criterion Integrity Evaluation
Auth Decision
!=
Criterion Update Response
Criterion Update Candidate
!=
Accepted Criterion
A central executable combination is:
AUTH_STABLE + FREEZE
The current authentication relation may continue while adaptation of the future authentication criterion is blocked.
Highlights
Guarded Criterion Trajectories
- Introduces Criterion Integrity Evaluation as a separate application-layer decision process.
- Represents authentication-criterion change as a guarded, traceable trajectory.
- Adds Criterion Update Responses:
ACCEPTDEFERFREEZEREVIEWROLLBACK
- Preserves the position:
dynamic criterion
!=
unconstrained self-update
Deterministic PoC
The release includes three fixed scenarios:
-
N1 — Legitimate New Device Transition
REAUTH_REQUIRED → AUTH_STABLE → AUTH_STABLEDEFER → ACCEPT → ACCEPT
-
P1 — Gradual Region Expansion Poisoning
- direct adoption expands the criterion until the attack reference becomes admissible;
- guarded adoption produces
DEFER → FREEZE → FREEZEand preserves the trusted criterion; - Stage 2 demonstrates
AUTH_STABLE + FREEZE.
-
C1 — Single Evidence Source Compromise
- apparently strong evidence does not override insufficient source integrity and weak cross-evidence consistency;
- the guarded response remains
FREEZE.
Relevant artifacts:
scripts/simulate_guarded_criterion_update.py
examples/criterion_update/scenarios.json
results/criterion_update_summary.json
Publication Artifacts
- English and Japanese Guarded Criterion Trajectories manuscripts.
- Canonically numbered figures 1–6.
- Automated PDF generation, A4/size/text/image checks, and repository commit workflow.
- English manuscript submitted to Jxiv and currently under review.
- Japanese manuscript prepared as a submission candidate.
Publication files:
publications/guarded_criterion_trajectories/jxiv_submission/
├── guarded_criterion_trajectories_en.pdf
└── guarded_criterion_trajectories_jp.pdf
GitHub Pages Research Demo
A static research demo is available at:
https://gitgyro-dev.github.io/gyroauth/
The demo provides:
- N1 / P1 / C1 scenario selection;
- stage-by-stage Auth Decision and Criterion Update Response;
- current criterion center and width;
- attack-reference admissibility;
- direct-versus-guarded comparison;
- explicit visualization of
AUTH_STABLE + FREEZE.
The demo uses HTML, CSS, Vanilla JavaScript, and static data only. It does not use an external API, backend service, production credentials, or real authentication telemetry.
Scope and Non-Guarantees
This release is a deterministic research implementation.
It is not:
- a production authentication service;
- a universal criterion-poisoning detector;
- a guarantee of zero false accepts or false rejects;
- a replacement for passwords, passkeys, MFA, authenticators, or assurance frameworks;
- a redefinition of Gyro Logic or the GyroOS runtime contract.
Layer Consistency
Gyro Logic = Theory
GyroOS = Execution System
GyroAuth = Authentication Application
- Gyro Logic Core remains unchanged.
- GyroOS runtime responsibilities remain unchanged.
- This release extends only the GyroAuth application layer with criterion-integrity evaluation, research artifacts, and visualization.
Links
- Live Demo: https://gitgyro-dev.github.io/gyroauth/
- Repository: https://github.com/gitGyro-Dev/gyroauth
- Previous Release: https://github.com/gitGyro-Dev/gyroauth/releases/tag/v2.0.0
- GyroAuth English paper: https://doi.org/10.51094/jxiv.4600
- GyroAuth Japanese paper: https://doi.org/10.51094/jxiv.5341
- Trajectory-Based Vulnerability Response: https://doi.org/10.51094/jxiv.5416
- Japanese vulnerability-response paper: https://doi.org/10.51094/jxiv.5440
GyroAuth v2.0 — Authentication as Stability-based Selection (PoC Release)
GyroAuth v2.0 — Authentication as Stability-based Selection
This release marks the first working Proof of Concept of GyroAuth.
GyroAuth is an authentication system where identity is evaluated not by exact matching, but by stability under deviation.
🔥 What’s New
-
FastAPI-based authentication API
-
Multi-slice observation model (Space / Time / Device / Behavior / Network / Motion)
-
Stability-based decision engine
-
Continuous authentication states:
- AUTH_STABLE
- RECONVERGING
- AUTH_FAIL
-
Real-time stability visualization
-
End-to-end working PoC
🧠 Core Concept
Authentication = Stability-based Selection
Instead of:
Match → Success / Fail
GyroAuth performs:
Observe → Deviation → Stability → Selection → Auth
⚙️ What This Release Demonstrates
- Identity can remain valid under deviation
- Authentication is continuous, not binary
- Stability collapse corresponds to attack scenarios
- Re-convergence is possible before failure
📊 Included Demo
- FastAPI PoC (
/observe,/authenticate) - Multi-step session simulation
- Stability timeline graph
- Attack scenario reproduction
🔗 Repository
https://github.com/gitGyro-Dev/gyroauth
🔴 Key Insight
Identity is not a fixed value.
It is a stable trajectory.
🚧 Notes
- GyroOS integration is currently abstracted
- Stability computation is simplified for PoC
- Future versions will connect directly to GyroOS
🎯 Purpose of This Release
This is not a theoretical concept.
This release demonstrates that:
👉 Stability-based authentication is implementable
👉 Identity can be evaluated as a dynamic system
🔚 Final Statement
Authentication is not about perfect reproduction.
It is about whether identity still holds under change.
GyroAuth v1.5 — From State Convergence to Executable Authentication
GyroAuth v1.5
From State Convergence to Executable Authentication
Overview
This release transforms GyroAuth from a conceptual framework into an executable proof-of-concept (PoC).
While previous versions introduced authentication as state convergence, this version demonstrates how the idea can be implemented as a working system.
What’s New
1. Full Authentication Pipeline
A complete pipeline has been implemented:
GyroAuth v1.3 — Authentication as State Convergence
GyroAuth v1.3
This release aligns GyroAuth with Gyro Logic v2.0:
https://doi.org/10.5281/zenodo.19555020
Authentication is defined as:
State Convergence
Status
- Theory connected
- Concept clarified
GyroAuth v1.2 — Authentication as State Convergence
GyroAuth v1.2 — Authentication as State Convergence
This release refines GyroAuth from a conceptual model into a structured convergence-based authentication framework.
GyroAuth redefines authentication as a continuous process:
Authentication = State Convergence
Instead of verifying static credentials, GyroAuth evaluates whether a user's state continuously converges across time, space, motion, and device context.
Key updates in v1.2:
- Formalized convergence-based authentication model
- Integration of dynamic state evaluation (continuous authentication)
- Introduction of trajectory-based identity representation
- Time-decay model: authentication validity decreases over time
- Multi-dimensional convergence (space, time, motion, device)
- Initial alignment with underlying theoretical framework (Gyro Logic)
Core principles:
- Authentication is not a point, but a trajectory
- Authentication is not static, but continuously evaluated
- Stolen credentials become useless over time
- Identity emerges from stable behavioral convergence
This version focuses on:
- Conceptual clarity
- Structural consistency
- Readability for both technical and non-technical audiences
We are currently exploring:
- Proof of Concept (PoC) implementations
- Security architecture applications
- Licensing and commercial use cases
Status:
Concept → Structure → Early Implementation
GyroAuth represents a shift from authentication as verification to authentication as dynamic convergence.
GyroAuth v1.1 — Authentication as State Convergence
GyroAuth v1.1 — Authentication as State Convergence
This release introduces the core conceptual model of GyroAuth:
- Authentication is not a point, but a trajectory
- Authentication is not static, but converging
- Authentication decays over time
This version includes:
- Core concept definitions
- State convergence model
- Visual diagrams (Trajectory / Convergence / Time Decay)
- Initial architecture direction
GyroAuth reframes authentication from static verification to dynamic convergence across time, space, motion, and device context.
We are exploring:
- Proof of Concept implementations
- Security architecture applications
- Licensing opportunities
This is an early-stage conceptual release.
GyroAuth v1.0.0 — Initial Public Concept Release
This is the first public release of GyroAuth, a GyroLogic-based authentication framework.
GyroAuth redefines authentication as:
multi-dimensional state convergence across space, time, motion, and device context.
Key idea:
Authentication succeeds only when the correct state exists at the correct place and time.
This release includes:
- Concept definition
- Mathematical model
- Core architecture
- PoC design
- Business positioning
Relationship to GyroLogic:
https://github.com/gitGyro-Dev/gyroos
Note:
This is not a production implementation.
This repository provides a protocol and conceptual architecture.
Vision:
Authentication is no longer about secrets.
It is about existence in space-time.