IAPont / Guides and resources

The document first. The tool second.

Explore the principles behind IAPont: visible source, browser-based document processing, explicit actions, portability and documented limits.

Keep the source visible

IAPont starts from a simple principle: a document should remain understandable and recoverable outside the interface that produced it. Markdown is used as the working reference because it remains readable, portable and transformable.

The browser as a workspace

Opening, editing, previewing and exporting are designed to happen in the browser. This does not mean the website works without a server: the browser still needs to load the application and required resources. The Privacy, Security and Transparency pages document the relevant limits.

No mandatory AI

The main workflow does not require a connected LLM to write, preview, check or export a document. A feature should not be labelled as AI when a deterministic transformation is sufficient.

Explicit actions

IAPont aims to avoid silent changes. Previewing is not publishing. Suggesting is not applying. Importing does not guarantee a perfect conversion. Users should be able to distinguish what they see from what actually changes the source.

Keep an exit path

A document tool should make it possible to continue working elsewhere. Exports and source preservation reduce dependence on a particular interface. IAPont does not describe this portability as absolute technological independence.

RAG, context and memory

Preparing passages and metadata can support RAG workflows. The OAM reflection goes further by considering context, relationships, provenance and how information changes over time. IAPont does not claim to solve all of these topics by itself.

State the limits

A candidate feature, a local test, an external score or the absence of an alert does not become a certification. IAPont should distinguish what is available, what has been tested, what still needs measurement and what remains a future direction.

Version 1.8.8 candidate: review the verification report before deployment.