The Sunlight Foundation Blog
 
  • Executive Transition Projects

    POSTED BY
    John Wonderlich

    Sometimes the most potent advocacy tool is a well formed list.  This is what makes Sunlight’s Insanely Useful Websites so popular, in addition to being so, well, useful).

    I’ve been tracking and sorting several fields of work relevant to transparency and civic information, and would like to share these lists, with the hope that similar efforts can benefit from each other.

    I’d like to start with a list of executive transition projects.  While any whitepaper or policy proposal could, in some sense, count as an executive transition project, there are a number of projects preparing proposals and principles for the next administration that focus on process and public involvement, engaging in the operations and management of government, and have implications for the potential roles an engaged public might play in a newly organized executive. (more…)

    0 Comments

    Posted: August 8th, 2008 Tags:
  • Oversight on the Office of Legal Counsel and Secrecy

    POSTED BY
    John Wonderlich

    After previewing it first, I attended last Wednesday’s Hearing by the Constitution Subcommittee of the Senate Judiciary Committee about “Secret Law and the Threat to Democratic and Accountable Government.”

    For fuller coverage, see FireDogLake, the Guardian, ACS Blog, or the statements and testimony from the hearing (set off on the upper right).

    While my coverage will be far from complete, I find the process of taking and then preparing my notes from committee hearings to be a great way to digest what was presented, and to start to work through some of the issues that relate to open government and accountability, which lie at the heart of this hearing. (more)

    The hearing started right into defining this distinction, with John Elwood, the Deputy Assistant Attorney General, making two sharp distinctions: First, he contended that the OLC memos were legal advice, not binding law, and, second, that Congress didn’t need to see the actual OLC memos in order to understand the policy under which the executive branch is operating.

    Much of the hearing addressed this distinction. Is the term “secret law” appropriate? Insofar as OLC memos are binding on those they proscribe, and insofar as some regulations such as TSA regulations literally affect a citizen’s conduct, then there is “secret law”.

    Senator Whitehouse? and Mr. Elwood went back and forth a few times on the degree to which OLC memos are a certain kind of admissable document in a court, trying to distinguish what kinds of legal evidence or legal usage the OLC memo might have the possibility of becoming. Senator Whitehouse accused the Bush Administration of using the OLC memos as a way of making cover for the rest of the agencies, which the operate under (technically illegal) legal advice.

    If you’re getting legal advice, you want it to be be objective. This is why the recent IG reforms that passed the Senate and House incude a provision to provide IGs with separate legal counsel. How objectively can one do oversight when your legal advice is coming from the office you’re investigating?

    The issue here is between the Congress, which is like the IG, needing to do effective oversight on the Department of Justice, where the Office of Legal Counsel writes their memos. If Congress can’t see the memos, or sometimes gets to see them, but only alone, without staff, and can’t take their notes with them, then how is that oversight? If they get to see individual pages, or even individual sentences, but not the rest of the documents, how can they perform their legislative duties?

    There was a pleasant part of the hearing, where Senator Brownback? and Senator Feingold? realized they agreed on a limited measure that would require reporting of a certain kind from the executive branch when they interpret the law differently than it looks, which, as the rules now stand (apparently), is required only when the executive decides to not carry out the law. Both reporting requirements have the same effect; when the President avoids something viewed as unconstitutional, whether through interpretation or through denying any execution at all, Congress should have the right to be notified, since this is a clear violation of the intent of the legislation.

    Senator Whitehouse’s testimony brought up some troublesome issues with executive power, especially dealing with the relationship between the President and the Department of Justice, and between Executive Orders and current Presidential conduct. The disturbing section follows, go here for an on screen version;

    1. An executive order cannot limit a President. There is no constitutional requirement
    for a President to issue a new executive order whenever he wishes to depart from the terms
    of a previous executive order. Rather than violate an executive order, the President has
    instead modified or waived it.
    2. The President, exercising his constitutional authority under Article II, can determine
    whether an action is a lawful exercise of the President’s authority under Article II.
    3. The Department of Justice is bound by the President’s legal determinations.

    While I’m not a legal scholar, the principles discovered here by Senator Whitehouse show an executive that is claiming expansive power, and, in turn, making the task of citizen oversight nearly impossible, in some circumstances. While the struggle and negotiations that go on around disclosure boundaries will probably not stop, they’re likely to shift a little when people realize that oversight and disclosure documents can offer real substance.

    It’s easy to shirk a responsibility to share when no one cares. If people are empowered in their role as overseers, as watchdogs, then perhaps memos like these don’t get written.

    0 Comments

    Posted: May 5th, 2008 Tags: , , , , ,
  • On Government Documents Management

    POSTED BY
    John Wonderlich

    Building on my earlier post about listing collaborative options for government or congressional agencies, I’m thinking about useful ways to distinguish between different types of government information, and what that implies about records management.

    At the recent IPDI Politics Online panel on radical transparency, Peggy Garvin made a great point about one fundamental distinction that can be made within government information. She suggested that all government information is either collected from regulated entities, or pertains to the operations of government itself. (much more below)

    Other fundamental distinctions could be made about government information generally; for example, all government information is either classified or not (attempt to equivocate notwithstanding.)

    Reflecting on this point, I thought of the various Creative Commons designations to be asserted over works. These distinctions have been developed as technology made use and reuse of (especially) digital information easier by an order of magnitude, which, in turn, rendered previous regulatory systems inadequate both de jure and in spirit. The same could now be said of both privacy law and many privacy policies, whose phrasing is too vague to apply clearly to new digital circumstances. (Technology that changes rapidly can be a real headache for legislative drafting: for example, the line between terms of art and informal slang is fuzzy at best.)

    Back to government information, the same thing that happened to music because of mixtapes, and that happened to video because of youtube, is also happening to government information. Regulatory schemes and records management practices need to be rethought.

    What would a forward looking government information management system look like? FDSys, obviously, is the new federal documents delivery system, but I’m wondering about the new policy distinctions that are probably on their way.

    For example, some documents have enough public import and enough consistent demand that they should be published online as quickly as possible, in as structured a way as possible. Votes in legislatures would fall under this distinction. Another set of documents would be those things that exist under the domain of the government, and maybe are FOIA-able, but are probably best not public. Personnel information and yearly reviews all online would make for a very complex work environment.

    I suspect that people at the GSA or OMB spend their time making exactly this sort of documents management distinction for the federal government, and if anyone has public documents or OMB memos to this effect, I’d love to see them. These management practices, however, are probably based on old legislative mandates like the paperwork reduction act or the OMB A-130 circular.

    I’m thinking about something more far-reaching, that could proactively assign distinctions to documents with public access in mind, in addition to other concerns like national security, or commercial or private or sensitive information. Another example, which information sets within the governmental (there are more than a few) are appropriate for APIs? Surely there’s a better way to decide on this than on a case-by-case basis. Which documents should have permanent URLs associated for them? If NIST can dictate that congressional districts will be referred to as "AL - 01" (or whatever), then shouldn’t someone make similar statements about government URL/database structures?

    If the US gets a CTO, (or, if the structures in place to carry out these functions are expanded), that person or those people should come into the job realizing that they’re not just coordinating technology, but they’re practical epistemologists, determining in practice what can be known about our national government.

    (Full Disclosure: Larry Lessig is on Sunlight’s Advisory board, although I had no contact with him about this post.)

    0 Comments

    Posted: March 12th, 2008 Tags:

The Site may contain links to Internet sites that are not operated by Sunlight Foundation. These links are provided as a service and do not imply any endorsement of the activities or content of these sites, nor any association with their operators. Sunlight Foundation does not control these Internet sites and is not responsible for their content, security, or privacy practices. We urge you to review the privacy policy posted on web sites you visit before using the site or providing personal information.


The content of this site, where applicable, is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License.