Choose the visual treatment only. Layout, evidence, links and provenance remain independent and can be changed separately.
FULL WIDTH is the default canvas. STANDARD BODY constrains the report for conventional reading. AUTO columns are calculated from the actual rendered width and update on resize.
Focus rebuilds approved article/body semantics into an Ashlight-owned reader. Remote scripts, CSS, forms, frames, ads, trackers, cookie surfaces and arbitrary embeds are not mounted into the workspace.
v31.7B still uses direct source image URLs when media is enabled. A later service layer can relay/cache permitted media, calculate actual binary cost, strip unwanted metadata, embed self-contained assets or capture a rendered figure snapshot while retaining provenance.
Repository profiles remove repeatable site-shell material from the normal research projection without deleting the retained semantic source record. Profiles are intentionally source-specific and only promoted after a repeatable pattern is verified.
FocusDocumentV1.sourceBlocks / sourceFullText, but the ordinary reader, query surface and human export operate on the cleaned repository projection.These defaults affect standalone FocusDocument HTML only. They do not delete source material from FocusDocumentV1 or the research reader.
EXACT searches for the supplied word or phrase as a contiguous normalized occurrence inside the selected document region. It does not require the whole BODY / TITLE / ANY TEXT record to equal the entered value.
Focus SEARCH.WEB now defaults to an account-free DuckDuckGo no-JS discovery adapter. SOURCE.OPEN remains a separate retained-result acquisition step, so search snippets stay candidates rather than evidence. SearXNG and Brave remain installed as dormant provider paths instead of being deleted when infrastructure/account requirements are unavailable.
Ashlight uses DuckDuckGo only as the upstream discovery service. The provider page is not embedded. Search results are parsed server-side, normalized into typed Ashlight objects, and SOURCE.OPEN remains a separate confirmation step.
Presentation belongs to Focus, not the upstream provider HTML. Link and visited-link colours follow the active Focus theme. Sponsored status is retained and visibly labelled in both projections.
DuckDuckGo is treated as an independent upstream service with its own privacy, advertising and safe-search policies. Ashlight's typed projection does not rewrite those policies; it makes the interchange boundary visible.
The adapter stays in Ashlight, but this shared host cannot run the resident SearXNG service we tested for. Enable later with a reachable SearXNG instance on a VPS/container and set ASHLIGHT_SEARCH_PROVIDER=SEARXNG plus ASHLIGHT_SEARXNG_URL (or search_config.json).
The HTTPS adapter remains installed but inactive unless you deliberately choose it later. Enabling it requires a Brave Search API account and a server-side API key. No browser/localStorage secret is used.
RSS/Atom is the canonical recurring-information branch for the current shared host. Ashlight fetches public feed XML server-side, projects text metadata only, and requires an explicit FEED.SOURCE.OPEN step before a feed item is treated as inspected source content.
Origins live under the preserved Ashlight data root, not inside overwrite packages. They are explicit subscriptions: adding a URL is a deliberate information-distribution choice, not inferred interest.
Feed content remains the same typed PublicFeedItemV1 projection. These controls only change how Focus presents retained feed metadata in this browser.
RSS-Bridge is not bundled into Ashlight. On a compatible shared host it can live in its own sibling/tool folder. Ashlight does not need a special privileged integration: a bridge-generated RSS/Atom URL is added as a normal public origin and enters the same sanitizer/source-confirmation pipeline.
These are not the shared-host canonical path. Their contracts can remain documented/dormant and be activated later without replacing DuckDuckGo + Feed.
Semantic activity only. Mouse movement does not keep a session active. The interval after a meaningful Focus action is ACTIVE, then QUIET / READING, then IDLE. These defaults apply when the next Session Archive starts.
Reports use the existing Ashlight Export Treatment renderer. These options borrow its themes and layouts instead of creating a second report branch.
Archive management lives here rather than filling the main Focus panel. Delete affects sealed Session Archives only; an active recording cannot be deleted.
A reversible local relevance layer for the result list. It does not fetch extra pages, remove results, change source evidence or claim that a highly ranked source is more truthful. It only asks: how strongly does this returned item appear to match the current crawl query?
The initial trial follows the Advanced Query build contract. Scores are normalised within a common 0–100 relevance scale rather than directly comparing the older source-specific raw scores.
Ashlight targets capability parity, not artificial sameness. Every source should reach the deepest level its lawful/technical access permits, and the Atlas must say where it stops.
Source-specific changes are deliberately surfaced here and in the machine changelog so future agents can reuse the same recovery techniques when a source returns zero useful results.
New repositories should be registered once, declare access/auth/policy, implement normalized search and optional hydration/evidence/media adapters, then surface through the same capability registry to Focus, Rabbit, Director and future agent transports.
Focus is a domain-neutral research workbench for retrieving bounded source material, reducing a working set, inspecting relationships, capturing attributed evidence and producing clean research outputs. Retrieval, evidence, presentation and future agent control remain separate authorities.
The search gateway is installed but its current provider is deployment-gated on this host.
{ }
Major open/public research repositories, archives, official databases and discovery systems are grouped by subject role. Integration status is explicit: LIVE means Focus can use it now; PROBE means this fork has a bounded test adapter; ADAPTER means the source is valuable but deserves a dedicated connector; KEY means credentials are required; POLICY means access/licensing or crawl behaviour needs explicit review. The atlas is intentionally broad and expandable rather than science-only.
Probe Lab V2 defaults to no workspace mutation, but can explicitly project clearly labelled metadata-only previews. It supports fixture, custom-query and custom-set modes, broad candidate pools, Rabbit query-fitness vetting, dedupe, bounded promotion and a reproducible preflight receipt before deep acquisition.
A bounded provider adapter sits behind Focus. DuckDuckGo no-JS search is the account-free default; SearXNG and Brave remain dormant provider paths for later deployment. Search results are candidates, not evidence. Opening a source is a separate SOURCE.OPEN acquisition step with its own URL/hash/bytes/retrieval evidence.
Public HTTP(S) GET only for source inspection. The configured search adapter may make its fixed upstream search request (DuckDuckGo uses its public no-JS form POST), but no arbitrary external POST, crawl, mutation, credential, deployment or iframe authority is granted. Every opened source must originate from a retained search result.
SOURCE.OPEN waits for an explicit result selection.
Fetch a public RSS/Atom origin through Ashlight. Feed items are candidates until explicitly opened as source content. The browser receives normalized metadata and optional Ashlight-proxied feed images only.
DuckDuckGo for intentional discovery · RSS/Atom for recurring/current feeds. Saved origins are your favourites; the starter catalogue is only a first-class selector, not an inferred subscription.
FEED.SOURCE.OPEN waits for an explicit item selection.
Git repositories are versioned source corpora and code/documentation systems. Focus registers repositories, pins source revisions, applies rights/index policy, builds local indexes and exposes only bounded capabilities to products and agents.
Approved public repositories may be acquired anonymously or by the Ashlight system identity. Personal/private repositories are excluded unless explicitly connected and selected. Tokens belong in a server-side credential vault — never localStorage, exported HTML, agent prompts or room transcripts.
Public repositories can be registered without a personal account. Registration is not ingestion: Focus records the URL and intended policy first, then a server worker performs bounded acquisition after preflight.
These principals are intentionally non-transitive. The safer architecture is a GitHub App for Ashlight system access, a separate user-auth flow for the Director's personal account, and no direct GitHub credential at all for Accord agents.
Used for approved public repositories where Git/archive/raw/API access does not require authentication. Ideal for public-domain/open datasets and documentation.
Installation-scoped system identity for named repositories. Default permission should be repository metadata + contents READ. Write permissions are a separate future grant, not part of indexing.
Your personal GitHub account may later be connected for your repositories and actions. Signing into the Ashlight Director does not automatically connect GitHub, and the resulting token is not exposed to Accord agents.
Agents access Git through Ashlight's bounded verbs and local/public indexes. They never need a GitHub password, PAT, private key or reusable OAuth bearer token.
Focus should index public repositories as pinned source snapshots, not as anonymous blobs. Every indexed document keeps repository, path, commit SHA/release, content hash, licence evidence and retrieval time.
Resolve branch/tag to a commit SHA. Index against that immutable revision and record any later update as a new snapshot.
Repository visibility is not a licence. Preserve repository licence plus item-level rights where files/assets differ.
Public source visibility permits reading where allowed; it does not grant agents remote write or contribution authority.
Accord agents receive verbs, never credentials. Private-repository reads and every remote mutation require an explicit repository-bound capability. Remote write remains disabled in this build.
| ACTION | PUBLIC READER | ASHLIGHT APP | DIRECTOR PERSONAL | ACCORD AGENT |
|---|---|---|---|---|
| discover public repo | YES | YES | YES | VIA GIT.PUBLIC.SEARCH |
| read public file/tree | YES | YES | YES | VIA GATEWAY |
| index approved public repo | OPERATOR POLICY | YES | NOT PERSONAL BY DEFAULT | REQUEST / RECEIPT |
| read private repo | NO | SELECTED INSTALL ONLY | USER-BOUND | EXPLICIT TASK ENVELOPE |
| create local worktree | NO | LOCAL ASHLIGHT | LOCAL ASHLIGHT | GIT.WORKTREE.OPEN |
| propose patch | NO | STAGE ONLY | STAGE ONLY | GIT.PATCH.PROPOSE |
| push / merge remote | NO | OFF BY DEFAULT | DIRECTOR EXPLICIT | NO DIRECT CREDENTIAL |
Discover public repositories / indexed documents without granting account authority.
Read a repository/tree/file only within an explicitly named public or granted repository.
Search Focus's local immutable public-repository indexes; preferred agent research path.
Retrieve revision, hash, rights and provenance for a locally indexed source snapshot.
Create a bounded local staging worktree. Does not create remote authority.
Produce a candidate patch in Workbench for Director review; no remote mutation.
This becomes the operator-visible audit stream for repository registration, index snapshots, auth binding changes and future remote requests. Secrets are never written into receipts.