Reference¶

Reference pages describe exact commands, APIs, editable contracts, generated wrapper behavior, and generated build files. They assume you have already built a wrapper — start with Getting Started and the User Guide if you have not.

Drive PRIK¶

• CLI commands — every command, option, and checked workflow.
• Python API — the build entrypoints and advanced package imports.
• Build manifests and Makefiles — how both files are generated, what they contain, and how to build or replay them.

Contracts¶

• .pyi Format — project and namespace structure, declarations, C and Fortran forms, decorators, native calls, types, storage, and metadata.
• Editing .pyi contracts — the complete supported editing workflow.
• Exports and modules — names, visibility, and package shape.
• Functions and classes — methods, overloads, and constructors.
• Calls and results — native call order, arguments, mutation, and results.

The contract pages describe the shared generated Python surface. Start from a contract generated for the same native implementation, then rebuild and call the changed path once.

Check support and diagnostics¶

• Fortran Support — the complete map of supported Fortran wrapper areas, limits, and detailed guides.
• C Support — the complete C source, contract, build, generated API, and support-boundary workflow.
• Language feature matrix — whether a feature is supported at all, with its evidence.
• Diagnostic codes — what a rejected wrapper is telling you and which stage owns the rejection.