# App manifest reference

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** App manifest  
**Availability:** Documented and testable

> The source contract and local workflow exist. Access still depends on the target hospital deployment and its policy gates.

`medos-app-project/1` is strict authoring metadata; `medos-remote-app-release/1` is the signed immutable release envelope.

## What you can use now

- Validate both schemas and keep authority-shaped fields out of the project file.
- Bind app ID, publisher, version, URL, origin, artifact digest, protocol, and signing key in the release.

## Current limits

- Neither manifest grants scopes, entitlement, certification, or activation.

## Next step

Start with the [medOS Developer overview](/developers/platform/overview) and confirm the target hospital’s enabled contracts before production work.

## Canonical references

- [FHIR R4 integration](/integrations/fhir)
- [Public API](/backend/public-api)
- [Security and compliance](/architecture/security-and-compliance)
- [Developer portal status and coverage](/developers/platform/changelog)