Troubleshooting and current limits

I cannot sign in or save a project in the browser

Use app.seifprotocol.com over HTTPS with cookies enabled. New accounts need a name, an email address and a password of at least 12 characters. The free workspace holds three projects; a fourth creation or import is refused. Account lets you update your name or password. Changing a password closes other sessions. The initial browser release has no self-service password recovery or email verification; contact support if you lose access.

If a save reports a conflict, another edit changed that file. Reload it, compare the text and reapply your change. If a save rejects a source, check for an absolute path, .. traversal, remote connector, runtime provider, malformed YAML or likely credential. Cloud projects may read only project-contained sources. Keep secrets in local vault/environment bindings, never in knowledge files.

Preview or a test does not include my document

Check four things in order: the file exists under the source folder; its frontmatter names the intended layer; the consumer/objective selects a profile with that layer; and its section fits the retrieval and token budget. Preview shows the reason for each excluded layer. A required test can return FAIL or UNKNOWN. UNKNOWN means the expected fact could not be established; it is not a pass. The token count is an estimate, not a provider invoice.

If a Build refuses to proceed, run Validate and read its exact blocking finding. Fix the source observation or required test, then validate the candidate again. A Build made before the edit remains immutable; create a new one.

Import or local launch fails

The cloud Import project accepts its JSON export format, seif.cloud-project.v1. Extract a ZIP and open the folder locally; do not upload the ZIP to the JSON importer. Import creates a new project and does not copy Build directories, cloud sessions or credentials. A local project with out-of-folder paths, remote sources or runtime providers needs those settings adapted before cloud import.

The published desktop installer is macOS arm64. Verify the installer checksum before opening it. Because version 0.6.0 is ad-hoc signed and not notarized, macOS can require System Settings → Privacy & Security → Open Anyway after the first attempt. On a different operating system, use a supported local build/source checkout until a verified installer is published.

A model answer is wrong although my test passed

Context Tests prove structural expectations about selected/rendered material, not the quality of a model answer. Add an agent scenario with an explicit answer expectation, evaluate it against the exact model connection and review the result. A generated response can vary across runs. A Context Trace can explain what SEIF delivered, but it cannot claim internal model consumption without application-side reporting. Report uncertain consumption as UNKNOWN and investigate the application request separately.

The initial hosted Context Lab does not include team sharing, billing, model-backed Agent Workspace, remote data connections, cloud deployment or hosted trace investigation. Those broader workflows currently run in the local Workstation or standalone server. Capability comparison.