ANTRequest's Foundation Specification (Version 0.1.0)

The ANTRequest's Foundation Specification (Version 0.1.0) Standard is a Meta Standard that defines things all other ANTRequest Standards use.

to use ANTRequest's Foundation Specification (Version 0.1.0) you can use This Specification to insure interoperability. If you do not Like where this is going please fork.

warning! For History Only

Table Of Contents

Status of this document

this document written on Wed Mar 11 2026 is Semantic version 0.1.0. this document is self-published independently.

i am still Figuring things out. this is not final design and might be vague, impossible, or otherwise not implementable. im still seeking to bring this closer to my vision.

This Specification uses external references

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Global Rules

All interactions MUST follow these global rules. If these rules are violated, the Implementation MUST abort the interaction and MAY notify the user (if any).

Applications MUST NOT connect to plain HTTP, Applications SHOULD try to change HTTP to HTTPS.
when a 404 or 500 is encountered Edges MUST read the Content-Type Header, if it states text/html the Edge SHOULD ignore the body and state the feature isnt supported to the user.
Info! on shared hosting 404 or 500 with a text/html mimetype is the default response for a file missing. when a file is missing the Planet cannot properly handle this interaction
Signature Verification MUST be done using the bytes As-Is (As Received), no Normalization, Canonicalization, Encoding change, or altering is allowed.
Info! This is important due to almost all algorithms assuming the bytes havent been altered at all. swapping the keys or changing indentation of a JSON or anything else will break the signature.
Normalization and Canonicalization is complex, and difficult. by Requiring no alteration, i can save a lot of difficulties for those that dont want to. You can Pretty Print it after you verified the thing.
Most Languages and Libraries come with JSON parsers, they do not come with JSON Canonicalization Engines. Most Languages and Libraries come with cryptographic functions that work on bytes. so by not allowing JSON Canonicalization at all, i can save a lot of difficulties for those that dont want to. and again, You can Pretty Print it after you verified the thing.
Interactions MUST be in the encoding UTF-8.

Definitions

Planet: A Server Implementing is called a Planet.
Edge: A Client Implementing is called an Edge. an edge is a client that interacts with the planet. could be a browser extension, the browser, or an app.
Implementation: A software instance of an Edge or Planet or both.
The Protocol: The Protocol as set forth in This Specification.
The Specification: The Specification is this htmlpage.
/Favicond_/: The Base Path of the protocol interactions. the underscore is a MUST. this path is directly after the domain.
REQUIRE: RFC2119's REQUIRED
Edge-Defined
Planet-Defined: A feature whose specific behavior is determined by the host environment rather than this specification. While this document may provide constraints, the Planet or Edge is free to define the exact behavior within those bounds.
Edge-Approximated
Planet-Approximated: A feature whose specific behavior is determined by the host environment rather than this specification. While this document may provide constraints, the Planet or Edge is free to define the exact behavior within those bounds, but preferably reacts like the recommending an ideal behavior.