# Self-service access and permission boundaries

Public SDK 0.3.9 and the [downloadable examples](https://docs.ammora.org/guides/example-setup) require
no GitHub invitation or npm authentication. The [agent quickstart](https://docs.ammora.org/guides/agent-quickstart),
[full agent guide](https://docs.ammora.org/guides/agent-launchpad), source files and settings template
are available on this public site and the [public examples repository](https://github.com/AmmoraLabs/ammora-examples).

## Choose the right permission path

The [full approval and review matrix](https://docs.ammora.org/guides/permissions) is shared by every integration guide. Wallet signatures, ERC20 allowances and local review hashes are your application's authorization, not Ammora customer approval.

| Your flow | Direct integration | Separate review or authority |
| --- | --- | --- |
| Native launchpad/agent | Valid Config, supported quote/helper and actual wallet/fee rights | New quote policy, custom helper or privileged settings |
| Ordinary stablecoin pool | Supported pair/preset, or supported probe for an unclassified exact-transfer token without an owner override | Owner policy blocking the operation, new preset or unsupported asset/issuer controls; pool admission does not grant aggregation admission |
| External revenue source | [Enabled-standard self-service](https://docs.ammora.org/guides/self-service), real holder consent and its actual ticket delay | New implementation/standard, existing weighted-right changes or stopped-module recovery |

New addresses alone do not require a new standard. The [new-address GIWA qualification](https://docs.ammora.org/guides/docs-partner-perspective-giwa) completed direct registration, delayed activation, trades and six positive weighted payments with no new governance transaction. Its test module was stopped; the fixture proves neither real-issuer support nor independent custody. Do not copy it as a live trading target.

## Config and the default launch flow

An external developer needs **no individual Ammora approval** to create a valid
reusable Config and use the supported-WETH launch flow on GIWA. The direct
caller must be `configOwner`. Config validation enforces valid economics and
the actual recipient/LP settings. A new entry starts enabled, without a second
per-team approval transaction. Config values are immutable; create a new Config
when you need different values.

Other Creators can use an enabled Config without the owner's key or registrar
status. The factory creates and policy-registers the new launch token. The shared
Config forwarder is deployment wiring for that factory, not a partner gateway
allowlist. A contract wallet must actually execute its transaction; an EOA
cannot impersonate it with an SDK field.

Live GIWA simulations at block **40349159** succeeded from an external address
that was neither Registry/factory owner nor a token-policy registrar: own Config
creation, token issuance from another owner's Config, and Config-plus-issuance.
Foreign-owner impersonation was denied. These were `eth_call` checks, without
keys or persisted external entries. The prior actual run also created Config
#23 atomically; the [qualification summary](https://docs.ammora.org/guides/agent-validation) separates
that transaction from simulations and historical direct Config evidence.

## Permissions that still apply

| Action | Actual authority or condition |
| --- | --- |
| Config, default supported-quote issuance, trading | Your wallet signs, owns input funds and sets its own allowances/slippage |
| Agent policy and transaction approval | Your application's owner chooses the local limits and authorized actions |
| Creator/Partner fees | Claimant owns that entitlement; payout destination grants no ownership |
| LP delegated fees | The actual fee authority for the selected manager grants the needed permission; NFT approval alone does not confer every fee right and an unrelated wallet remains denied |
| New quote asset | Factory requires both pool and aggregation-token policy support |
| Custom callback | Global code/policy approval; the built-in GIWA first-buy helper is already enabled |
| Config disabling/global policy changes | Protocol governance authority; Config ownership is not Registry administration |

SDK installation and Config creation do not grant every admin function or admit
every arbitrary token. A standard-token probe does not override aggregation
policy. No such protocol policy or contract change is part of this publication.

Choose your own fee, LP and leftover recipients explicitly. Copying a template
without replacing those fields keeps its existing beneficiaries. Funding,
wallet consent and LP delegation are different from Ammora customer approval.
