Configuration & settings

Two layers, on purpose:

	Configuration	Settings
Where	config/griglia.php, .env	/settings, stored in the database
Who decides	the developer who installs the package	whoever uses the board
When it changes	at deploy (config:cache)	at run time, immediately
What it covers	routes, models, disks, modes, gates, integrations	how the agent works, token saving, board behaviour

php artisan vendor:publish --tag=griglia-config     # config/griglia.php
php artisan vendor:publish --tag=griglia-views      # override the Blade views
php artisan vendor:publish --tag=griglia-lang       # translations (en, it)
php artisan vendor:publish --tag=griglia-agents     # AGENTS.md, the rules for the agent

Every field of /settings saves by itself, with no «Save» button: the switches when you click them, the selects, numbers, texts and times as soon as they change (a toast confirms it).

Settings the agent reads

The agent and optimization groups are not decoration: griglia:check prints them at the top of its output and the agent is expected to follow them — commit policy, question level, notifications, one task at a time or several, terse mode, response tone and response length. Change them from the page and the next griglia:check obeys. Clear and structured is suitable for experienced programmers too: it preserves technical detail while reducing unnecessary jargon, explaining unavoidable terms and using readable formatting.

Agent comment controls only the report stored below a task; Response tone and Response length control user-facing communication. Terse mode remains a separate token-saving choice and, when enabled, takes priority by reducing chat almost entirely.

Question level (autonomy) is a five-step scale — autonomous agent, a few essential doubts, ask questions, ask many questions, paranoid — that says how many questions the agent asks (--ask) before it really starts a task. Each step has its own rules: the page previews the context block of the selected step and, when you save, writes it into the agent context (/context → the generated instruction files) as a block generated from Settings; griglia:check prints the same rules under the settings line (❓ question level), so the agent reads them on both channels.

The language of the board

The board speaks the languages it is translated into — English (base) and Italian — and the App group of /settings opens with the choice:

• As in the application (EN) — the default: the board follows config('app.locale'), so a host application that sets the locale by itself (a SetLocale of its own, a per-user preference) keeps deciding.
• English, Italiano, … — one entry per language folder found in the package's resources/lang and in the published lang/vendor/griglia: publish your own translations and they appear here.

The choice applies to every board page and to the Livewire requests behind modals and saves, dates included («3 hours ago») and the texts of the generic themes (the «add a task» button, the «write here…» placeholders, the counter — see Themes). It does not touch the console: griglia:check keeps talking to the agent in English.

Adding a language is a folder next to en and it — see Translations.

The full inventory

Generated from the code, so it never lags behind:

• Configuration file — every key, its environment variable and its default.
• Settings — every option of the three groups, with the help text of the page.
• Settings backlog — what is deliberately not there yet.

Access, administrators and the local mode have their own page: Access & modes; the seams your app can hook into — views, strings, themes, styles, events — are in Extending Griglia.