ANTRequest's Foundation Specification (Version 0.3.0)

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

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

Table Of Contents

Table Of Contents

Status of this document

this document written on Thu Mar 12 2026 is Semantic version 0.3.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 MUST try to change HTTP to HTTPS.

• If TLS fails or Certificate is not valid, the Edge MUST abort the connection.

• 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.

• Signature Verification MUST be done using the bytes As-Is (As Received), no Normalization, Canonicalization, Encoding change, or altering is allowed.

• Interactions MUST be in the encoding UTF-8.

Philosophy

FaviSpecs MUST follow these principles.

• Promote Fork Build Deploy
• features must contribute and help everyone, or at least the 90% majority. and by that i mean
  • do the complaints raise a security vulnerability?
  • do the complaints raise an ambiguity that should have been standardized?
  • do the complaints raise ways in how the standard became illegal to implement as written?
  notice how feature requests are not on that list?
• the body who accepts features must be capable of saying to go fork if it doesnt satisfy these requirements.
• if the protocol is feature complete there shouldnt be more features except for security bugs.
• when targeting a singular use cases, use a different standard which is normative optional.
• if the loud majority still is unsatisfied with the no, the body should stay their ground and say to fork.
• nobody is a not an exception to the rules.
• paying for addition of features must not be accepted.
• it SHOULD work on a Storage Supported Host.
• it MUST work on a Standard Supported Shared Host.

Storage Supported Host

A Storage Supported Host MUST (including but not limited to)

• Access to At Least 1 Actively Supported PHP Version.
• Access to HTTPS. An SSL/TLS certificate is Required for this.
• Access to a way to persistent data storage.
• Access to the file system. readonly is reasonable but readwrite is better.
• Access to a secure Cryptographically Secure Pseudo Random Number Generator.
• Access to JSON parsing and writing.

Standard Supported Shared Host

A Standard Supported Shared Host MUST

• Qualify for Storage Supported Host.
• Access to the database via php.
• Access to the file system with readwrite permission.
• Access to a way to redirect End User URLs to Actual Files (for example mod_rewrite).
• Access to setting the following Headers (including but not limited to):
  • HTTP Strict Transport Security.
  • Cache-Control.
  • All CORS Response headers.
  • Content-Type.
  • Content-Security-Policy.
  • Content-Security-Policy-Report-Only.
  • Link.
  • Last-Modified.
  • Set-Cookie.
  • Vary.
  • WWW-Authenticate.
  • Custom Headers.
• Access to getting the following Headers unmodified (including but not limited to):
  • Authorization
  • All CORS Request headers.
  • Content-Type.
  • Cookie.
  • X-Content-Type-Options.
  • Custom Headers.
• Access to a secure cryptographical Library. at time of writing: including but not limited to:
  • libsodium - for Ed25519 signatures and XChaCha20-Poly1305 encryption.
• MUST NOT alter body bytes in transit.

Definitions

FaviSpecs

The specifications on this site.

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.

Ai Acknowledgement

Thanks to DeepSeek Gemini, Grok, and ChatGPTfor guidance writing all these specifications while proofreading (except LayerZip).