2 guides
netweft's cache and rate limiter fail open: a cache that cannot answer is a miss, and a limiter that cannot count lets the request through, so the product keeps working, more slowly and more permissively. Choosing that up front is what stops a performance dependency becoming an availability one.
netweft's SEO data provider is an interface with two implementations: DataForSEO for real data, and a mock serving deterministic fixtures with no credentials. Nothing above the port knows which answered, so the product runs offline, every test is deterministic, and credit accounting is identical on both paths.
May we set cookies to see how netweft is used? Session recordings never capture what you type. Nothing is stored until you answer, and declining still counts the visit, without a cookie. Privacy